Summary: Intermittent browser/components/extensions/test/browser/test-oop-extensions/browser_ext_contextMenus_icons.js → Intermittent browser_ext_contextMenus_icons.js | Test timed out
this is failing on win7/8 opt in e10s mode only, not debug at all. with 21 failures yesterday, this is pretty high on our radar to get a fix. :andym, is there a chance you can find someone on the webextensions team to get a fix in over the next 2 weeks for this?
Whiteboard: [stockwell needswork]
it looks like we see a pair of failures often and the failure in the onclick test is tracked in bug 1346039. I would prefer to focus on this bug and see this fixed first as it might end up fixing bug 1346039.
:mattw, this is failing very frequently (21 failures yesterday alone! + failures from bug 1346039), are you close to figuring this out, or should we disable the test temporarily?
It looks like the failure started happening right around the time that bug 1318791 landed.
After looking into this more, it looks like both the onclick and icon tests seem to timeout waiting for closeExtensionContextMenu to resolve. Tomislav, could you take a look into bug 1302742 and bug 1333403 to see if either of those might be causing this issue? Thanks!
(In reply to Matthew Wein [:mattw] from comment #15) > Tomislav, could you take a look into bug 1302742 and bug 1333403 to see if > either of those might be causing this issue? Thanks! It's unlikely bug 1333403 is related, as it didn't touch any of those tests, nor change any of the implementation timings. Looking at the test for bug 1302742, I guess there could be a async timing issue there, in which case we would likely need a round trip through the extension after the menus are created, something like this: http://searchfox.org/mozilla-central/source/browser/components/extensions/test/browser/browser_ext_contextMenus.js#321-326
:mattw, it sounds like possibly bug 1302742 could be related, is this something that you or :zombie can get a fix for soon? The failure rates are pretty high and we are on track for 100+ failures this week. I don't mind temporarily disabling this on windows+!debug until there is more time to fix this if that is desired.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/13ce1c218795 Intermittent browser_ext_contextMenus_icons.js. temporarily disable on win/opt. r=gbrown
Whiteboard: [stockwell needswork] → [stockwell disabled]
Comment on attachment 8880997 [details] Bug 1351638 - Fix intermittents caused by menus_commands test https://reviewboard.mozilla.org/r/152356/#review157412 I don't think this is going to help. A round trip shouldn't be necessary here, and the failure screenshot clearly shows that the item has been added to the context menu, but the sub-menu isn't open. So it seems like the problem has to do either with the code that waits for the top-level context menu to open, or the code that attempts to open the sub-menu. If I had to guess, I'd guess that it's because the context menu is animated open on Windows, and the click event doesn't make it to the sub-menu item. But that's mostly just a guess.
I suspect when we fix this test we will fix bug 1346039 as well
So, this was never a problem with menus_icons test (or menus_onclick), but instead with menus_commands intermittently failing to close the top level context menu, as seen in this screenshot: https://public-artifacts.taskcluster.net/IZHOsQy4Qe6rMuDD5sEWgg/0/public/test_info/mozilla-test-fail-screenshot_7yuvmm.png I've tried to figure out what's actually causing the menu to remain open, but gave up after a dozen or so tries with various timeouts and requestAnimationsFrames(), and instead just ensured the menu gets closed manually every time. At least Try seems happy: https://treeherder.mozilla.org/#/jobs?repo=try&revision=63f67d0e631c&duplicate_jobs=visible
Comment on attachment 8880997 [details] Bug 1351638 - Fix intermittents caused by menus_commands test https://reviewboard.mozilla.org/r/152356/#review159672 ::: browser/components/extensions/test/browser/head.js:337 (Diff revision 19) > let popupHiddenPromise = BrowserTestUtils.waitForEvent(contentAreaContextMenu, "popuphidden"); > EventUtils.synthesizeMouseAtCenter(itemToSelect, modifiers); > - return popupHiddenPromise; > + await popupHiddenPromise; > + > + // Bug 1351638: parent menu fails to close intermittently, make sure it does. > + contentAreaContextMenu.hidePopup(); Shouldn't this be before the `await popupHiddenPromise`?
Attachment #8880997 - Flags: review?(kmaglione+bmo) → review+
Comment on attachment 8880997 [details] Bug 1351638 - Fix intermittents caused by menus_commands test https://reviewboard.mozilla.org/r/152356/#review159672 > Shouldn't this be before the `await popupHiddenPromise`? We always get the `popuphidden` from the extension's context menu closing, it's the top level context menu that remains open sometimes, so this works.
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/6b24ed47a268 Fix intermittents caused by menus_commands test r=kmag
Whiteboard: [stockwell disabled] → [stockwell fixed:other]
Resolving as any intermittents remaining are likely unrelated to the original issue.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Removing leave-open keyword from resolved bugs, per :sylvestre.
You need to log in before you can comment on or make changes to this bug.