Closed
Bug 1393676
Opened 8 years ago
Closed 7 years ago
test_ext_options_ui.html is going to permafail on Android x86 when Gecko 57 merges to Beta on 2017-09-20
Categories
(WebExtensions :: Android, defect, P1)
Tracking
(firefox57- verified)
VERIFIED
FIXED
mozilla57
People
(Reporter: RyanVM, Assigned: rpl)
References
Details
Attachments
(1 file)
[Tracking Requested - why for this release]: Permafailing test on the next merge day.
Android x86 only from the looks of it.
https://treeherder.mozilla.org/logviewer.html#?job_id=125745971&repo=try
INFO TEST-UNEXPECTED-FAIL | mobile/android/components/extensions/test/mochitest/test_ext_options_ui.html | Test timed out.
INFO TEST-UNEXPECTED-FAIL | mobile/android/components/extensions/test/mochitest/test_ext_options_ui.html | Extension left running at test shutdown
Flags: needinfo?(lgreco)
Comment hidden (mozreview-request) |
Assignee | ||
Comment 2•8 years ago
|
||
I've tried to reproduce it locally (by pulling from the merge test linked above and building Fennec on Android x86 locally), and even if I'm not able to reproduce a permafail locally, I'm able to see it failing intermittently by running the test file using "./mach mochitest ... --run-until-failure".
From the debugging session that I've been doing locally, it seems that the timeout is related to a race between
the `BrowserApp.closeTab` calls used in the test to close the tabs and `BrowserApp.selectOrAddTab` (used in both the test and in `runtime.openOptionsPage` when open_in_tab is true):
`BrowserApp.closeTab` sends a request to the Java side to remove the tab, but the actual tab object is removed from the "tab deck" only when BrowserApp receives the reply from the Java side, while `BrowserApp.selectOrAddTab` will try to select an existent tab from the "tabs deck" if it is still there (even if it is going to be removed soon as an effect of the BrowserApp.closeTab call).
It probably has an higher chance to happen on Android x86 because the emulator is way faster than the ARM one.
I'm attaching a patch which applies some changes to the options_ui test cases to avoid this kind of race conditions.
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Flags: needinfo?(lgreco)
Priority: -- → P1
Assignee | ||
Updated•8 years ago
|
Attachment #8901192 -
Flags: review?(mixedpuppy)
Comment 3•8 years ago
|
||
mozreview-review |
Comment on attachment 8901192 [details]
Bug 1393676 - Fix intermittent timeout failures on options_ui Android tests.
https://reviewboard.mozilla.org/r/172658/#review178178
Attachment #8901192 -
Flags: review?(mixedpuppy) → review+
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/34a4eebfa165
Fix intermittent timeout failures on options_ui Android tests. r=mixedpuppy
Comment 5•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
This is fixed, no need to track it.
Reporter | ||
Updated•7 years ago
|
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•