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 mark.dickinson
Recipients aimacintyre, eric.smith, gpolo, mark.dickinson, r.david.murray, skrah, vstinner
Date 2010-04-19.12:55:45
SpamBayes Score 4.6713292e-05
Marked as misclassified No
Message-id <1271681747.75.0.98347734721.issue8424@psf.upfronthosting.co.za>
In-reply-to
Content
> Can't we try to increase the timeout step by step? Eg. 5 sec => 10 sec, > then 15 sec, etc. until the buildbots turn green?

I think you'd need an increase of an order of magnitude or two (possibly more) in some cases to make this work:  notice that the failure message from the itimer_virtual test gives an indication of how much virtual time *has* actually passed, and in some cases it's none at all (to within the timer resolution).

Also, this doesn't seem like a very future-proof solution.

Reducing the time intervals (0.2, 0.3, ...) probably isn't much of an option either:  I'd expect difficulties with timer resolution.
History
Date User Action Args
2010-04-19 12:55:48mark.dickinsonsetrecipients: + mark.dickinson, aimacintyre, vstinner, eric.smith, gpolo, r.david.murray, skrah
2010-04-19 12:55:47mark.dickinsonsetmessageid: <1271681747.75.0.98347734721.issue8424@psf.upfronthosting.co.za>
2010-04-19 12:55:46mark.dickinsonlinkissue8424 messages
2010-04-19 12:55:45mark.dickinsoncreate