A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-March/062289.html below:

[Python-Dev] Developing/patching ctypes

[Python-Dev] Developing/patching ctypes [Python-Dev] Developing/patching ctypesThomas Heller theller at python.net
Sun Mar 12 12:13:07 CET 2006
Thomas Wouters wrote:
> On 3/10/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Thomas Heller 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?
>> They are now in
>>
>>
>> http://www.python.org/dev/buildbot/all/amd64%20gentoo%20trunk/builds/280/step-test/0
> 
> 
> I suspect that some of those failures probably aren't ctypes failures, but
> re-running-ctype-tests-in-the-same-process failures (like the very first
> one) -- I get more errors when running -R:: than I do when running the test
> verbosely directly.

I can reproduce that now - thanks for finding the problem.  IMO, some of the ctypes tests
are kind-of broken, since they keep state although they should not.

> Maybe re-running the test could be done in a freshly
> spawned Python?

I'll try to fix the ctypes-tests starting on Monday, so I assume that would
not be necessary.

Thomas

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4