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 r.david.murray
Recipients pitrou, r.david.murray
Date 2009-10-16.18:51:11
SpamBayes Score 2.5747182e-12
Marked as misclassified No
Message-id <1255719076.69.0.751832436592.issue7151@psf.upfronthosting.co.za>
In-reply-to
Content
In certain circumstances output written to stderr during a test comes
after the json result string the -j code is expecting to see at the end
of the returned subprocess output.  This causes that regrtest worker
thread to fail.  This problem is more acute on py3k; perhaps the new io
library is more likely to delay output of stderr.

Attached is a patch that avoids the problem by capturing stderr
separately.  This means that all stderr output will be after all regular
output, which changes the output of the test suite slightly (eg: in a
debug build all the refcount messages come after the output from
test_subprocess).  This seems like a small enough issue that it isn't
worth the code complexity required to code around it, especially since
the ordering of the interleaving of the two streams isn't guaranteed
even without -j.
History
Date User Action Args
2009-10-16 18:51:16r.david.murraysetrecipients: + r.david.murray, pitrou
2009-10-16 18:51:16r.david.murraysetmessageid: <1255719076.69.0.751832436592.issue7151@psf.upfronthosting.co.za>
2009-10-16 18:51:14r.david.murraylinkissue7151 messages
2009-10-16 18:51:12r.david.murraycreate