1522900 - adjust reftest and wpt manifests to run on windows 1803

Status: RESOLVED FIXED

(Testing :: General, enhancement)

Description

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

in migrating to windows 10 1803, there are updates we need to make to wpt manifests to use the specific version and a small number of reftests that need adjusting.

Comment 1

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

here is a try push:

Comment 2

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

here is a try push:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=84eb962be0ac680db29a06088be70ad9710131aa

Comment 3

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

Attachment: Bug 1522900 - adjust manifests to allow tests to pass on windows10 1803 release. r=ahal

adjust manifests to allow tests to pass on windows10 1803 release

Comment 4

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

The webrender 0-255 fuzz seems excessive. Do you have a try push showing that failure?

Comment 5

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

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

Comment 6

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

Those all look like failures. Can you mark them fails-if instead of fuzzy-if?

Comment 7

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

Attachment: Bug 1522900 - adjust manifests to allow tests to pass on windows10 1803 release. r=gbrown

adjust manifests to allow tests to pass on windows10 v1803

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0277af3f283d
adjust manifests to allow tests to pass on windows10 1803 release. r=gbrown CLOSED TREE

Comment 9

[Cristian Brindusan [:cbrindusan]]

https://hg.mozilla.org/mozilla-central/rev/0277af3f283d

Comment 10

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-beta/rev/cc418f03e319

Comment 11

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-release/rev/c890bfaae769

Comment 12

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-esr60/rev/437c332ac6f2

Comment 13

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-beta/rev/2be696cf1253
https://hg.mozilla.org/releases/mozilla-beta/rev/2e610b19a641

Comment 14

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-esr60/rev/f49ec9a97e14

Comment 15

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-beta/rev/0a00de2cff5f

Comment 16

[Sylvestre Ledru [:Sylvestre]]

Is it possible to backout these changes until we published the releases?
This bug forces us to take the patch in bug 1513145 and we don't feel comfortable about that.

Comment 17

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

I didn't realize there was a release- is there a schedule and if this is an emergency release when is an ideal time where we shouldn't have an emergency release? On top of that if we backed out and then relanded bug 1513145 on release/esr later this week, would it be ok? We don't get test coverage on those branches as we would be back in this same spot next week, next release, etc. How would we be ok with landing that change after this unscheduled release?

A work around is to create a small pool of 1703 windows machines which we can use for release/esr and then we can backout the changes on release/esr and add a small patch to use the old windows worker.