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 db3l
Recipients db3l, paul.moore, pdgoins, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-05-17.20:50:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526590240.94.0.682650639539.issue33355@psf.upfronthosting.co.za>
In-reply-to
Content
A longer timeout might be another workaround, but for myself, I tend to favor Zachary's original suggestion of eliminating largefile tests for the moment as simplest and most robust.  It would also reduce the overall percentage of test time currently spent on a small number of tests.

Time (and budget) permitting, I do hope to try some tests on newer Azure machine types to see if they behave differently, which might be a longer term option.
History
Date User Action Args
2018-05-17 20:50:40db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, pdgoins, zach.ware, steve.dower
2018-05-17 20:50:40db3lsetmessageid: <1526590240.94.0.682650639539.issue33355@psf.upfronthosting.co.za>
2018-05-17 20:50:40db3llinkissue33355 messages
2018-05-17 20:50:40db3lcreate