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 neologix
Recipients neologix, phlogistonjohn, vinay.sajip
Date 2012-04-22.18:42:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0932f2_J4F_sCA9Ffm2TPAOBGv8V-C0TA5G39+W9S5eA@mail.gmail.com>
In-reply-to <1335116825.32.0.639130319143.issue14632@psf.upfronthosting.co.za>
Content
> There's certainly a problem to be addressed here, but integrating the test into the regular test suite represents a problem in that the test takes around 10 minutes to run, and sometimes completes successfully. I'm not sure a 10-minute extension of the time taken to run regrtest will be acceptable, but if the test is skipped unless explicitly enabled, then I'm not sure it'll add much value.

There's no reason to wait for 10 minutes: one can reduce the number of
iterations greatly, so that it can run in a matter of seconds. Since
the test is run by all the builders multiple times per day, should the
race condition resurface, it will trigger a buildbot failure some day.
No need for it to trigger a failure every time.
History
Date User Action Args
2012-04-22 18:42:19neologixsetrecipients: + neologix, vinay.sajip, phlogistonjohn
2012-04-22 18:42:18neologixlinkissue14632 messages
2012-04-22 18:42:18neologixcreate