Open Bug 1438663 Opened 2 years ago Updated 11 months ago
_ext _popup _focus .js | Test timed out -
This is a regression from bug 1324255. Shane, please take a look.
Looking into it, haven't been able to reproduce yet.
Assignee: nobody → mixedpuppy
This has hit the failure rate for disable-recommended tag with 175 failures from 15ht February until now. https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1438663&startday=2018-02-15&endday=2018-02-18&tree=all Shane, do you still want to try and fix this or should we disable it for now? Thanks.
Lets go ahead and disable. I was able to finally reproduce it last week but will have to track it down.
Priority: -- → P1
Hello! Made a patch for disablng this test for now as it has a really big number of failures. Please look over it to see if it's ok. Thank you.
Attachment #8952645 - Flags: review?(aryx.bugmail)
Comment on attachment 8952645 [details] [diff] [review] disable_bug1438663.patch Review of attachment 8952645 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/components/extensions/test/browser/browser-common.ini @@ +119,4 @@ > [browser_ext_popup_background.js] > [browser_ext_popup_corners.js] > [browser_ext_popup_focus.js] > +skip-if = true # Bug 1438663 Please use the 'disabled' keyword https://dxr.mozilla.org/mozilla-central/source/testing/mozbase/docs/manifestparser.rst#54-68
Attachment #8952645 - Flags: review?(aryx.bugmail) → review-
Modified it. Thanks.
Attachment #8952652 - Flags: review?(aryx.bugmail) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/391296e5323f Disable browser/components/extensions/test/browser/test-oop-extensions/browser_ext_popup_focus.js for frequent failures. r=aryx
Whiteboard: [stockwell disable-recommended] → [stockwell disabled]
Moving to p3 because no activity for at least 24 weeks. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.