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 brian.curtin, gvanrossum, sbt, tim.golden, vstinner, yselivanov
Date 2014-02-21.17:50:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393005026.63.0.275659849293.issue20720@psf.upfronthosting.co.za>
In-reply-to
Content
> After all the test does use run_briefly(), which might as well be renamed run_with_race_condition().

Oh, it means that the "Future/Task exception was never retrieved" is a just a consequence of the failed assertion.

IMO the run_briefly() should be avoided, whereas it is used in many places. For example, the protocol used in test_create_server() should provide a future to wait until the protocol is connected.
History
Date User Action Args
2014-02-21 17:50:26vstinnersetrecipients: + vstinner, gvanrossum, tim.golden, brian.curtin, sbt, yselivanov
2014-02-21 17:50:26vstinnersetmessageid: <1393005026.63.0.275659849293.issue20720@psf.upfronthosting.co.za>
2014-02-21 17:50:26vstinnerlinkissue20720 messages
2014-02-21 17:50:25vstinnercreate