[Python-Dev] Test failures under Windows?

Kristján Valur Jónsson kristjan at ccpgames.com
Tue Mar 31 23:49:03 CEST 2009

I found a different problem in multiprocessing, for the py3k.
In import.c, get_file.c, it was knowingly leaking FILE objects, while the underlying fh was being correctly closed.  This caused the CRT to assert when cleaning up FILE pointers on subprocess exit.
I fixed this this afternoon in a submission to the py3k branch.


-----Original Message-----
From: Jesse Noller [mailto:jnoller at gmail.com] 
Sent: 31. mars 2009 21:31
To: Kristján Valur Jónsson
Cc: Curt Hagenlocher; mhammond at skippinet.com.au; David Bolen; python-dev at python.org
Subject: Re: [Python-Dev] Test failures under Windows?

2009/3/31 Kristján Valur Jónsson <kristjan at ccpgames.com>:
> Right, my question to microsoft was more about making sure that a __crtMessageBox() actually does nothing, when running unattended as a service.
> Also, we should be seeing the same problem in non-debug versions, since the _set_invalid_parameter_handler() is no longer called, and the default one also puts up a message box.  The Assertion is then performed _in_addition_ on debug builds:
> >From ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_vccrt/html/c0e67934-1a41-4016-ad8e-972828f3ac11.htm
> In the following example, an invalid parameter error handler is used to print the function that received the invalid parameter and the file and line in CRT sources. When the debug CRT library is used, invalid parameter errors also throw an assertion, which is disabled in this example using _CrtSetReportMode.
> Btw, I am working on finding out the test suite failures for test_multiprocessing.
> K

I spoke to Martin about this yesterday, apparently a specific test in
the multiprocessing suite was triggering these dialogs (the test
invalid handle test). We're working on a patch for multiprocessing so
that the children will obey the flag


More information about the Python-Dev mailing list