regrtest -j fails when tests write to stderr

[bitdancer]

BPO	7127
Nosy	@pitrou, @ezio-melotti, @bitdancer
Superseder	bpo-7151: regrtest -j sometimes fails if output gets written to stderr by a test

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2009-10-18.17:07:52.643>
created_at = <Date 2009-10-14.16:07:02.431>
labels = ['easy', 'type-bug', 'tests']
title = 'regrtest -j fails when tests write to stderr'
updated_at = <Date 2009-10-18.17:07:52.459>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2009-10-18.17:07:52.459>
actor = 'r.david.murray'
assignee = 'none'
closed = True
closed_date = <Date 2009-10-18.17:07:52.643>
closer = 'r.david.murray'
components = ['Tests']
creation = <Date 2009-10-14.16:07:02.431>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 7127
keywords = ['easy']
message_count = 2.0
messages = ['94003', '94215']
nosy_count = 3.0
nosy_names = ['pitrou', 'ezio.melotti', 'r.david.murray']
pr_nums = []
priority = 'low'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '7151'
type = 'behavior'
url = 'https://bugs.python.org/issue7127'
versions = ['Python 2.7', 'Python 3.2']

[bitdancer]

If a test writes to stderr, then the -j (multiprocessing) support in
regrtest fails to correctly extract the JSON data from the test output,
resulting in a JSON traceback followed by a failure of the worker
thread. Antoine has suggested tagging the JSON result string with a
prefix and looking for that prefix, instead of the current method (which
assumes that the JSON result string is at the end of the output from the
test).

[bitdancer]

Hmm. Look like I forgot that I opened this issue, and opened a new one
with the patch. Closing this one in favor of the one with the patch.