This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients JelleZijlstra, benjamin.peterson, corona10, db3l, remi.lapeyre, serhiy.storchaka, stutzbach, vstinner
Date 2020-06-04.02:53:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It appears the recent commit is causing a CRT exception dialog in test_close_stdin (test_repl.TestInteractiveInterpreter).  The dialog can't get answered, which is what leads to the eventual timeout.

The assertion is "_osfile(fh) & FOPEN" from osfinfo.cpp on line 258.  It actually appears twice (if the first is ignored).  If both are ignored the test passes.

I was somewhat surprised to see the dialog, as I believe CRT exception dialogs are disabled during test runs (others are present in test logs).  Perhaps the child interpreter used by test_repl doesn't inherit that behavior.  If so, this was probably always a risk, there just weren't any assertions occurring before this in the child interpreter.
Date User Action Args
2020-06-04 02:53:35db3lsetrecipients: + db3l, vstinner, benjamin.peterson, stutzbach, serhiy.storchaka, JelleZijlstra, corona10, remi.lapeyre
2020-06-04 02:53:35db3lsetmessageid: <>
2020-06-04 02:53:35db3llinkissue40826 messages
2020-06-04 02:53:34db3lcreate