Closed Bug 1371698 Opened 2 years ago Closed 2 years ago
Permaorange in e10s a11y browser-chrome tests when Gecko 55 merges to beta on 2017-06-12
[Tracking Requested - why for this release]: merge bustage, closed tree, delayed b1 Something that landed in the last couple days is going to cause https://treeherder.mozilla.org/logviewer.html#?job_id=104745546&repo=try 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. https://treeherder.mozilla.org/logviewer.html#?job_id=105648799&repo=try https://treeherder.mozilla.org/logviewer.html#?job_id=105648807&repo=try
Eitan, can you please look at this as soon as possible? Thanks!
Need to push this to try first..
Attachment #8876427 - Flags: review?(wkocher)
Attachment #8876427 - Flags: review?(wkocher) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/330ef64c2e38 Don't run a11y+e10s tests on release branches of Windows. r=RyanVM
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.
Joel, 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?
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.