Changes by Stefan Krah stefan-use...@bytereef.org:
--
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1481
___
___
Stefan Krah stefan-use...@bytereef.org added the comment:
Issue fixed by test_uuid3.patch from issue 3581 in trunk (r79954),
release26-maint (r79959), py3k (r79960) and release31-maint (r79961).
--
assignee: - skrah
keywords: -needs review
resolution: - accepted
stage: patch review -
Stefan Krah stefan-use...@bytereef.org added the comment:
Still fails with trunk on OpenBSD. The error is more ctypes related
though: _uuid_generate_time isn't set.
==
ERROR: test_unixdll_getnode (__main__.TestUUID)
Stefan Krah stefan-use...@bytereef.org added the comment:
With test_uuid.patch from issue 3581 (related) no warnings can be seen on the
buildbots.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1481
A.M. Kuchling li...@amk.ca added the comment:
They were disabled in r50949, with the comment:
Disable these tests until they are reliable across platforms.
These problems may mask more important, real problems.
One or both methods are known to fail on: Solaris, OpenBSD, Debian,
Brian Curtin cur...@acm.org added the comment:
These tests have been disabled for a little over two years now. I've run the
previously disabled tests on Windows, Mac OSX, and Linux numerous times and
haven't seen any instability or failures (not that it proves much).
I wasn't around at the
New submission from Christian Heimes:
I'm putting the report into the tracker as a reminder.
WARNING: uuid.getnode is unreliable on many platforms.
It is disabled until the code and/or test can be fixed properly.
WARNING: uuid._ifconfig_getnode is unreliable on many platforms.
