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 vstinner
Recipients jkloth, vstinner
Date 2019-10-21.13:18:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> ... is not showing up when the test is re-run in verbose mode.

_force_run() logs require verbose >= 2. The test suite is run using:

'Tools\\buildbot\\test.bat' '-x64' '-j2' '-j4' '--timeout' '900'

which runs:

C:\\3.x.kloth-win64\build>"C:\\3.x.kloth-win64\build\PCbuild\amd64\python_d.exe"  -u -Wd -E -bb -m test  -uall -rwW --slowest --timeout 1200 --fail-env-changed -j1 -j2 -j4 --timeout 900 

Using this command, I get: support.verbose=1 in the main regrtest process and in regrtest worker processes.

Maybe _force_run() should always log, or log "if verbose:" (remove ">= 2" restriction).
Date User Action Args
2019-10-21 13:18:13vstinnersetrecipients: + vstinner, jkloth
2019-10-21 13:18:13vstinnersetmessageid: <>
2019-10-21 13:18:13vstinnerlinkissue38544 messages
2019-10-21 13:18:13vstinnercreate