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 ncoghlan, ned.deily, neologix, pitrou, r.david.murray, serhiy.storchaka, vstinner, zach.ware
Date 2014-03-13.21:20:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394745606.31.0.905882660234.issue20910@psf.upfronthosting.co.za>
In-reply-to
Content
"I don't like these patches at all. It is not obvious that making sleep times configurable improves things at all, and it's one more complication in the test suite that people will have to care about."

The default timings should choosen to work on most computers. The idea is to add an option for very slow buildbots. In my experience, sporadic test failures related to time only occur on a few buildbots. Sorry, I don't have the list, but most timing issues occur on between 3 or maybe 4 buildbots.


"I agree with Antoine.  There is never going to be a right value for sleep: the behavior of the buildbots can vary so much from run to run, especially if there are multiple VMs running on one host.  If anything, we should be working to remove as many "sleep" dependencies from the test suite as possible, not encourage their use."

Making tests faster is not my first target, it's just a side effect. My first goal is to make tests more reliable. I want all buildbots to be always 100% green.
History
Date User Action Args
2014-03-13 21:20:06vstinnersetrecipients: + vstinner, ncoghlan, pitrou, ned.deily, r.david.murray, neologix, zach.ware, serhiy.storchaka
2014-03-13 21:20:06vstinnersetmessageid: <1394745606.31.0.905882660234.issue20910@psf.upfronthosting.co.za>
2014-03-13 21:20:06vstinnerlinkissue20910 messages
2014-03-13 21:20:06vstinnercreate