➜

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 asvetlov, giampaolo.rodola, ned.deily, terry.reedy, vstinner, yselivanov
Date 2018-05-24.23:09:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527203373.57.0.682650639539.issue32458@psf.upfronthosting.co.za>
In-reply-to
Content 
It would be nice to fix this bug before Python 3.7.0 final: either skip the test, or fix it. Flaky tests can be very annoying. For example, the full test suite is run to build a Red Hat package. If a single test fails, the package build fails and should be retried whereas it's slow.

I understood that fixing the root cause might require to rewrite the test, so I don't expect a quick fix on this test. The issue is open since last December... Maybe we can skip the test but fix it in Python 3.7.1?
History
Date User Action Args
2018-05-24 23:09:33vstinnersetrecipients: + vstinner, terry.reedy, giampaolo.rodola, ned.deily, asvetlov, yselivanov
2018-05-24 23:09:33vstinnersetmessageid: <1527203373.57.0.682650639539.issue32458@psf.upfronthosting.co.za>
2018-05-24 23:09:33vstinnerlinkissue32458 messages
2018-05-24 23:09:33vstinnercreate