Author db3l
Recipients db3l, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-05-06.21:25:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525641949.1.0.682650639539.issue33355@psf.upfronthosting.co.za>
In-reply-to
Content
Nothing for my part, but there was an Azure "maintenance" on 4/16 where both the Win8 and Win10 buildbots were migrated to "newer" hardware (the first change to their physical machine for a really long time).  No word on why.  The VM machine class was unchanged, and the tests run on a local disk.  But perhaps there has been a performance or other impact (Spectre changes?)

That seems to line up in terms of timing, for example with Win10 3.x build 795 and Win8 3.x build 831 both running the AM of 4/16 with the first failures.

Oddly, I'm having trouble finding a reference to test_mmap in older Win10 3.x build logs, but on Win8 3.x builds it was definitely one of the slower tests before that point, although only in the 4-5 minute range.

So not sure.  Assuming it was the "upgrade" and given the persistence of the failure since, I suppose it's safer to assume this is a new normal for that platform - if skipping the particular test(s) would work, I say go for it at least for now.

-- David
History
Date User Action Args
2018-05-06 21:25:49db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2018-05-06 21:25:49db3lsetmessageid: <1525641949.1.0.682650639539.issue33355@psf.upfronthosting.co.za>
2018-05-06 21:25:49db3llinkissue33355 messages
2018-05-06 21:25:48db3lcreate