1526407 - 3 reftests fail when switching from windows10 1703 to windows10 1803

Status: RESOLVED WONTFIX

(Core :: Graphics: WebRender, enhancement, P3)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

as per bug 1522900 and a try push:
https://treeherder.mozilla.org/#/jobs?repo=try&searchStr=reftest-e10s%2Cwin%2Cqr%2Cdebug&revision=3b2654dcf6ffb8d7c5db26c84153085a133a6354

we have 3 failures on reftest from layout/reftest/bugs/reftest.list:
HTTP == 632423-1.html 632423-1-ref.html
HTTP == 579808-1.html 579808-1-ref.html
HTTP == 599476.html 599476-ref.html

Comment 1

[Jonathan Kew [:jfkthame]]

I was going to look and see what kind of failures were involved, but the logs from that try push seem to be missing - is there a known reason for that?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

frustrating, the log is only kept for 2 weeks and of course I worked on this on/off to get green tests before filing bugs and the timeout expired.

here is the change:
https://hg.mozilla.org/mozilla-central/rev/0277af3f283d#l11.32

and this ends up only being:
632423-1.html

and I added this condition:
fails-if(/^Windows\x20NT\x2010.0/.test(http.oscpu)&&webrender&&isDebugBuild)

so do something like:
./mach try fuzzy -q 'windows10-64 qr reftest-e10s'

you could remove that condition from the line- and use the above try command. likewise I am happy to do that and get a fresh log.

Comment 3

[Kartikaya Gupta (email:[e-mail])]

I retriggered the failure so we should get a new log on that try push shortly (maybe - I'm not sure if the build will get rebuilt or if it will just fail)

Comment 4

[Kartikaya Gupta (email:[e-mail])]

The job did finish but isn't showing the reftest failure. Not really sure why.

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

I see some other retriggers, lets see what those show- IIRC some of the tests I disabled where failing 2/3 times if not a higher percentage- usually seen over multiple pushes.

Comment 6

[Glenn Watson [:gw]]

These tests no longer exist in m-c.