Author db3l
Recipients db3l, paul.moore, pdgoins, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-05-23.22:14:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527113662.77.0.682650639539.issue33355@psf.upfronthosting.co.za>
In-reply-to
Content
The win7 builder isn't on Azure, so changing host type isn't an option at the moment.  For my part, I'd prefer removing the largefile tests for that one rather than increasing timeout.  The tests generate a huge amount of I/O, so my guess is it's just not practical in the current builder environment.

I should note that unlike the win8/win10 builders, there have been no VM or host changes for the win7 builder in quite a while, so if these failures are recent, they can't necessarily be explained by test environment changes.  With that said, the win7 builder is certainly resource constrained in terms of CPU and I/O so perhaps the tests were always marginal.  Or perhaps the use of -j2 is exacerbating the situation depending on which pair of tests overlap with test_mmap.
History
Date User Action Args
2018-05-23 22:14:22db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, pdgoins, zach.ware, steve.dower
2018-05-23 22:14:22db3lsetmessageid: <1527113662.77.0.682650639539.issue33355@psf.upfronthosting.co.za>
2018-05-23 22:14:22db3llinkissue33355 messages
2018-05-23 22:14:22db3lcreate