[Python-Dev] Developing/patching ctypes (original) (raw)
Thomas Heller theller at python.net
Fri Mar 10 22:15:47 CET 2006
- Previous message: [Python-Dev] Developing/patching ctypes
- Next message: [Python-Dev] Developing/patching ctypes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Neal Norwitz wrote:
On 3/10/06, Thomas Heller <theller at python.net> wrote:
BTW: The buildbot reports ctypes test failures on the gentoo amd64 machine:
http://www.python.org/dev/buildbot/trunk/amd64%20gentoo%20trunk/builds/277/step-test/0 Is there a way to get the actual failures somehow? Running the tests in verbose mode by default is probably not a good idea, because it may make tests fail, AFAIK. I want to modify regrtest so the traceback info is stored in a file, so you can still retrieve the data after a test run. I haven't started making this mod yet.
There are also sporadic test failures on the OSX machine:
http://www.python.org/dev/buildbot/trunk/g4%20osx.4%20trunk/builds/345/step-test/0
I think the test is broken - but what I find interesting is that in this case the actual failure is printed:
""" test_set test_ctypes test test_ctypes failed -- Traceback (most recent call last): File "/Users/buildslave/bb/trunk.4/build/Lib/ctypes/test/test_leaks.py", line 68, in test_cycles_refcount self.fail("leaking refcounts") AssertionError: leaking refcounts
test_long_future """
Why is that?
Thomas
- Previous message: [Python-Dev] Developing/patching ctypes
- Next message: [Python-Dev] Developing/patching ctypes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]