Closed Bug 1522900 Opened 2 years ago Closed 1 year ago

adjust reftest and wpt manifests to run on windows 1803


(Testing :: General, enhancement)

Not set


(firefox-esr60 fixed, firefox65 fixed, firefox66 fixed, firefox67 fixed)

Tracking Status
firefox-esr60 --- fixed
firefox65 --- fixed
firefox66 --- fixed
firefox67 --- fixed


(Reporter: jmaher, Assigned: jmaher)


(Depends on 1 open bug)



(2 obsolete files)

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.

here is a try push:

adjust manifests to allow tests to pass on windows10 1803 release

Blocks: 1515432
Blocks: 1525783
Blocks: 1525782

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

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

Blocks: 1525472
Depends on: 1525653
Depends on: 1526407
Depends on: 1526417
Depends on: 1526421
Depends on: 1526423
Depends on: 1526429
Depends on: 1526432
Depends on: 1526436
Depends on: 1526438
Depends on: 1526441
Depends on: 1526444
Depends on: 1526450

adjust manifests to allow tests to pass on windows10 v1803

Assignee: nobody → jmaher
Attachment #9039163 - Attachment is obsolete: true
Attachment #9042642 - Flags: review?(gbrown)
Pushed by
adjust manifests to allow tests to pass on windows10 1803 release. r=gbrown CLOSED TREE
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Attachment #9042642 - Flags: review?(gbrown) → review+
Depends on: 1527038

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.

Flags: needinfo?(jmaher)
Flags: needinfo?(gbrown)
Version: Version 3 → unspecified

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.

Flags: needinfo?(jmaher)
Flags: needinfo?(gbrown)
Attachment #9042642 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.