[issue27423] Failed assertions when running test.test_os on Windows

STINNER Victor added the comment: This bug has been fixed in test_os or libregrtest, I don't recall, but it's now fixed ;-) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue27423] Failed assertions when running test.test_os on Windows

Steve Dower added the comment: The warnings are expected - Python has to be able to handle arbitrarily bad parameters/use without crashing, while the CRT assumes that bugs belong to the direct caller who needs to fix them. As a result, it will assert and terminate for blatantly incorrect

[issue27423] Failed assertions when running test.test_os on Windows

Eryk Sun added the comment: test_os intentionally operates on invalid file descriptors. In the Windows CRT this leads to failed assertions, such as from its _VALIDATE_RETURN macro. This macro would also call the default invalid parameter handler, which would kill the process, but that's

[issue27423] Failed assertions when running test.test_os on Windows

Emanuel Barry added the comment: I'm not sure about the patch - sure, the messages might go away, but I find it concerning that the assertions are failing to begin with. Of course, it only happens when in debug (and this might be a non-issue in practice, I haven't checked), but shouldn't we

[issue27423] Failed assertions when running test.test_os on Windows

Changes by Serhiy Storchaka : -- nosy: +haypo ___ Python tracker ___ ___

[issue27423] Failed assertions when running test.test_os on Windows

Eryk Sun added the comment: The attached patch suppresses the failed-assertion message boxes when running test_os on a debug build. -- keywords: +patch nosy: +eryksun stage: needs patch -> patch review Added file: http://bugs.python.org/file43595/issue27423_1.patch

[issue27423] Failed assertions when running test.test_os on Windows

New submission from Emanuel Barry: Running test_os yields a ton (something like 20) failed assertion warnings. The attached screenshot is one of them (comes up a few times), but there are others. Choosing to Ignore the error makes Python think that the test was merely skipped without any