[issue3581] failures in test_uuid
report at bugs.python.org
Thu Apr 8 18:26:27 CEST 2010
Stefan Krah <stefan-usenet at bytereef.org> added the comment:
The new patch test_uuid.patch fixes issue 7650, issue 1481 and this one.
I've applied it to py3k-cdecimal in r79905 and test_uuid is passed
on all buildbots (I did not test on ARM and one FreeBSD bot is still hanging in test_subprocess).
Additionally, the patch works on Windows-qemu (this issue) and OpenBSD-qemu.
1. check_node accepts addresses with universal_local_bit set to 1.
These addresses are valid (like the qemu one).
2. check_node accepts addresses with the multicast bit set to 1.
These addresses are used for valid random addresses per the RFC
and uuid.getnode() itself actually may return such a random address.
3. On some platforms, _uuid_generate_time can't be set, so
_unixdll_getnode fails with a TypeError. This exception
is now caught.
4. With these changes, there appear to be no more failures, so
all tests are enabled again.
Could this go into trunk, since the tests actually fail needlessly
on qemu setups?
Added file: http://bugs.python.org/file16820/test_uuid.patch
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list