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 gvanrossum
Recipients brian.curtin, gvanrossum, sbt, tim.golden, vstinner, yselivanov
Date 2014-02-21.18:07:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393006047.71.0.509352831897.issue20720@psf.upfronthosting.co.za>
In-reply-to
Content
Agreed. I suppose all tests currently using run_briefly() should be modified to use run_until() with a lambda and a timeout. The timeout must be (a) large enough to never fail on a buildbot, yet (b) small enough that when a test is actually failing we don't mistake it for hanging. So I really would like to see a different pattern introduced -- but I'm at a loss for how to do it elegantly. (Ditto with the terrible hack for simulated time -- see http://code.google.com/p/tulip/issues/detail?id=128.)
History
Date User Action Args
2014-02-21 18:07:27gvanrossumsetrecipients: + gvanrossum, vstinner, tim.golden, brian.curtin, sbt, yselivanov
2014-02-21 18:07:27gvanrossumsetmessageid: <1393006047.71.0.509352831897.issue20720@psf.upfronthosting.co.za>
2014-02-21 18:07:27gvanrossumlinkissue20720 messages
2014-02-21 18:07:26gvanrossumcreate