Backport 196ede3d3505 to esr-10 to make Windows no-accel reftests work

RESOLVED FIXED

Status

()

Core
Graphics
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: philor, Assigned: philor)

Tracking

10 Branch
x86
Windows 7
Points:
---

Firefox Tracking Flags

(firefox-esr10 verified)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 615378 [details] [diff] [review]
fix

https://hg.mozilla.org/mozilla-central/rev/196ede3d3505 is the annotation changes that made it possible to unhide Windows reftests run without hardware acceleration. We need the same thing (minus bug482921-1.html since that's not on 10) on esr-10, so that we can stop wasting resources by running a hidden Ru, and start getting coverage to tell us that we broke something on a backport for people running without hwaccel.
Attachment #615378 - Flags: approval-mozilla-esr10?
(Assignee)

Comment 1

5 years ago
https://tbpl.mozilla.org/?tree=Try&rev=1c9c787b7de8 is the green try run, https://tbpl.mozilla.org/?tree=Mozilla-Esr10&noignore=1&jobname=reftest-no-accel is how we're currently wasting runs without seeing them.
Comment on attachment 615378 [details] [diff] [review]
fix

[Triage comment]
Approved, test-only fix.  Please go ahead and land as per https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
Attachment #615378 - Flags: approval-mozilla-esr10? → approval-mozilla-esr10+
(Assignee)

Comment 3

5 years ago
https://hg.mozilla.org/releases/mozilla-esr10/rev/eef6bfa5f495
Status: NEW → RESOLVED
Last Resolved: 5 years ago
status-firefox-esr10: --- → fixed
Resolution: --- → FIXED
Where can I go to check the ESR reftests to verify this is fixed?
Whiteboard: [qa?]
(Assignee)

Comment 5

5 years ago
https://tbpl.mozilla.org/?tree=Mozilla-Esr10&jobname=reftest-no-accel
(In reply to Phil Ringnalda (:philor) from comment #5)
> https://tbpl.mozilla.org/?tree=Mozilla-Esr10&jobname=reftest-no-accel

Thanks! Marking verified fixed based on this.
status-firefox-esr10: fixed → verified
Whiteboard: [qa?]
You need to log in before you can comment on or make changes to this bug.