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 Paul Monson, db3l, miss-islington, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-05-23.19:19:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558639180.8.0.995528951105.issue36511@roundup.psfhosted.org>
In-reply-to
Content
I've been investigating issues with test failures on my Windows buildbots seemingly not showing up in the master's web interface (but just showing warnings), and it appears likely due to this change.

For example, test_urllib (a test problem from issue 36948) was failing but only appeared as a warning (the first such case on my Win10 builder for example is https://buildbot.python.org/all/#/builders/3/builds/2661).

This change appears to force the exit code of test.bat to be successful (0) regardless of the results of the test run, thus obscuring any test failures from a parent process such as the buildbot.  As an aside, it also looks like any failures along the new arm32ssh branch would be obscured, assuming that the ssh operation would otherwise have propagated the remote exit code.

I think just leaving off the exit code (so just "exit /b") should propagate the rt.bat result properly.  Or, a goto to a label at the end of the file and letting it exit naturally would mimic the prior behavior.
History
Date User Action Args
2019-05-23 19:19:40db3lsetrecipients: + db3l, paul.moore, tim.golden, zach.ware, steve.dower, miss-islington, Paul Monson
2019-05-23 19:19:40db3lsetmessageid: <1558639180.8.0.995528951105.issue36511@roundup.psfhosted.org>
2019-05-23 19:19:40db3llinkissue36511 messages
2019-05-23 19:19:40db3lcreate