Closed Bug 1371698 Opened 5 years ago Closed 5 years ago

Permaorange in e10s a11y browser-chrome tests when Gecko 55 merges to beta on 2017-06-12


(Core :: Disability Access APIs, defect, P1)




Tracking Status
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 blocking fixed


(Reporter: ryanvm, Assigned: eeejay)



(1 file)

[Tracking Requested - why for this release]: merge bustage, closed tree, delayed b1

Something that landed in the last couple days is going to cause when we merge to beta on Monday. Unless there's an easy test-only fix, we should probably consider backing out the regressing patch at this point to minimize risk to the merge.
Eitan, can you please look at this as soon as possible? Thanks!
Flags: needinfo?(eitan)
bustage on merge day → marking as blocker for 55.
Need to push this to try first..
Attachment #8876427 - Flags: review?(wkocher)
Assignee: nobody → eitan
Attachment #8876427 - Flags: review?(wkocher) → review+
Pushed by
Don't run a11y+e10s tests on release branches of Windows. r=RyanVM
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
what was the problem here?  did we have failures, crashes, leaks?  I have been trying to get tests running on windows10 and I found that we are leaking in many of the a11y related browser-chrome tests.
Flags: needinfo?(eitan)

What are the specific steps you take locally to get these leaks? Do you change any of the manifests? Can you open a new bug for this?
Flags: needinfo?(eitan)
yes, let me get a bug opened; I have been working on narrowing down the leaks to specific tests, I was hoping to have that done today, probably tomorrow and I will get a new bug on file with instructions.
You need to log in before you can comment on or make changes to this bug.