➜

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 paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-05-09.13:59:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494338398.28.0.940820958867.issue30313@psf.upfronthosting.co.za>
In-reply-to
Content 
After my commit d2aff607199a24182714404777c80c7f180a35af of bpo-30283, test_regrtest failed with "multiple errors occurred; run in verbose mode for details" on "x86 Windows XP VS9.0 2.7" buildbot, but tests are not re-run in verbose mode on this buildbot :-(

See http://bugs.python.org/issue30283#msg293312

The "test" step of the buildbot runs directly the PC/VS9.0/rt.bat command which only pass -j2 option to regrtest.py, but not -uall -rwW.

Other Windows buildbots run Tools/buildbot/test.bat which pass -uall -rwW to regrtest.py.

I see different options:

* Modify PC/VS9.0/rt.bat to pass extra options: I dislike this option, it changes the behaviour, some people may rely on the current behaviour (and Python 2.7 is now considered as super stable)

* Copy Tools/buildbot/test.bat to PC/VS9.0/test.bat and modify the copy to run PC/VS9.0/rt.bat. I dislike this option, it duplicates code.

* Modify Tools/buildbot/test.bat to add an option to specify the pass to rt.bat and then modify the buildbot config to use test.bat instead of rt.bat but also use the new option to pass PC/VS9.0/rt.bat (or just "PC/VS9.0/" depending how the option is designed).

@Zach: I request your advice on this issue ;-)
History
Date User Action Args
2017-05-09 13:59:58vstinnersetrecipients: + vstinner, paul.moore, tim.golden, zach.ware, steve.dower
2017-05-09 13:59:58vstinnersetmessageid: <1494338398.28.0.940820958867.issue30313@psf.upfronthosting.co.za>
2017-05-09 13:59:58vstinnerlinkissue30313 messages
2017-05-09 13:59:57vstinnercreate