Description
Bug report
I already fixed errors related to non-ASCII skip messages (by using ascii()
instead of str()
or repr()
). There may be other non-ASCII skip messages left, but they are not raised on buildbots with non-UTF-8 stdout. In any case, this only fixed CPython tests, user tests can have the same issues.
#135121 exposed a new issue -- subtest description which includes non-ASCII parameter values. It is more difficult, because we have no control on formatting them. Always using ascii()
instead of repr()
will harm readability on normal platforms.
Activity
serhiy-storchaka commentedon Jun 4, 2025
The following tests passes in
unittest
and inlibregrtest
with a single process, but fails inlibregrtest
with multiple processes.When run with
unittest
, the output stream is stderr with the backslashreplace error handler. Inlibregrtest
with a single process, the output stream is stdout with the backslashreplace error handler, but in multi-process mode -- with the strict error handler.serhiy-storchaka commentedon Jun 4, 2025
cc @vstinner
pythongh-135124: Change stdout errors in regrtest worker process
pythongh-135124: Change stdout errors in regrtest worker process
pythongh-135124: Change stdout errors in regrtest worker process
vstinner commentedon Jun 4, 2025
I proposed #135138 to fix the issue.
11 remaining items