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 eric.snow
Recipients brett.cannon, eric.snow, jkloth, ncoghlan, pitrou, skrah, vstinner
Date 2012-08-25.18:31:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345919510.8.0.928394071568.issue15781@psf.upfronthosting.co.za>
In-reply-to
Content
So this was a random one-off (hardly even intermittent) failed test that passed on the retry.  Ah, threads.  Is there an easy way to find all other failures in test_threaded_import in the past, for this and for all buildbots?  Do we have information about load during tests?  Is there an easy way to run the test suite under load on a build bot?

With a large enough sample size we can make more sense of this.  For instance, do failures predate the addition of per-module import locks or the importlib migration in 3.3?  Are failures limited to particular platforms?  Is the problem load related?

BTW, test_threaded_import had another (different) failure a week ago on FreeBSD: issue15599.
History
Date User Action Args
2012-08-25 18:31:50eric.snowsetrecipients: + eric.snow, brett.cannon, ncoghlan, pitrou, vstinner, jkloth, skrah
2012-08-25 18:31:50eric.snowsetmessageid: <1345919510.8.0.928394071568.issue15781@psf.upfronthosting.co.za>
2012-08-25 18:31:50eric.snowlinkissue15781 messages
2012-08-25 18:31:49eric.snowcreate