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, ned.deily, paul.moore, pdgoins, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-05-24.19:16:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527189376.97.0.682650639539.issue33355@psf.upfronthosting.co.za>
In-reply-to
Content
For my buildbots, I suspect win8/win10 should be ok at this point.  Among any other changes their local disk appears to be an SSD now, which makes a big difference.  I observed steady 250-300MB/s write I/O for the duration of the mmap test, for example, so no wonder that test highlights any I/O bottlenecks.  

Those two buildbots are independent so it's more a question of running the tests at all versus just on one.

On the other hand, win7/winxp compete on the same host, with traditional disks.  So including winxp as a slow windows build together with win7 couldn't hurt, although as 2.7 only, winxp runs far fewer tests nowadays.
History
Date User Action Args
2018-05-24 19:16:17db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, ned.deily, pdgoins, zach.ware, steve.dower
2018-05-24 19:16:16db3lsetmessageid: <1527189376.97.0.682650639539.issue33355@psf.upfronthosting.co.za>
2018-05-24 19:16:16db3llinkissue33355 messages
2018-05-24 19:16:16db3lcreate