Intermittent comm/mail/components/extensions/test/browser/browser_ext_browserAction_popup_click.js | This test exceeded the timeout threshold.
Categories
(Thunderbird :: Add-Ons: Extensions API, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Assigned: john)
Details
(Keywords: intermittent-failure, intermittent-testcase)
Attachments
(2 files, 1 obsolete file)
Filed by: mkmelin [at] iki.fi
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=398725843&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/KqYk6n6nQyOgm89u6kY2KQ/runs/0/artifacts/public/logs/live_backing.log
Updated•3 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 15•2 years ago
|
||
We know we have issues with clicks on menu items and hiding menu popups
in the WebExtension tests. We currently mitigate these issues not only
in header files, but also directly in tests, and we also still have
places which are not using the mitigation (which could be the reason for
this intermittent).
While I still attempt to find the underlying cause for these issues,
this patch tries to unify the mitigation.
-
Use the helper
clickItemInMenuPopup()instead of manually calling
menu.activateItem()in the tests themselves. The helper waits for the
"popupHidden" event, which was not waited for in all places. -
Use the helper
closeMenuPopup()instead of manually calling
`menu.hidePopup() in the tests themselves. The helper waits for the
"popupHidden" event, which was not waited for in all places. -
The function
closeContextMenu()has been renamed to
closeBrowserContextMenuPopup()and no longer accepts a menu
parameter, but is now used only for the browserContext menu. If
a specific menu should be closed,closeMenuPopup()should be used. -
The function
closeExtensionContextMenu()has been renamed to
clickItemInBrowserContextMenuPopup(), which better describes what it
does.
Updated•2 years ago
|
| Assignee | ||
Comment 16•2 years ago
|
||
Another reason why this type of test could fail: We are not waiting till
the popup is closed but use a timeout.
This patch uses the helper closeBrowserAction() in all places,
which waits for the "popuphidden" event.
It also increases readability by using the named event "popup closed".
In the browser_ext_browserAction_popup_focus.js test, the
wait-for-closed logic is moved from the extensions background to the
test itself, because it is much more stable this way.
Depends on D204760
| Assignee | ||
Comment 17•2 years ago
•
|
||
This patch removes more arbitrary timeouts.
-
After
menu.activateItem()andmenu.hidePopup(), wait for an animation
frame instead of a fixed timeout. -
No longer wait 1s before closing the popup in the
run_popup_test()
function.
Depends on D204761
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 18•2 years ago
|
||
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/e6e1633e8d80
Unify clicks on menu items and hiding menu popups. r=mkmelin
https://hg.mozilla.org/comm-central/rev/3225ec8e3846
Properly wait for action popups being closed. r=mkmelin
Updated•2 years ago
|
Description
•