Intermittent test_ext_sendmessage_reply2.html | Test timed out. | Extension left running at test shutdown
Categories
(WebExtensions :: General, defect, P2)
Tracking
(firefox56 disabled, firefox57 disabled)
People
(Reporter: KWierso, Assigned: rpl)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure, Whiteboard: triaged [stockwell fixed])
Attachments
(2 files)
Updated•9 years ago
|
Updated•9 years ago
|
Updated•9 years ago
|
Comment 2•9 years ago
|
||
Updated•8 years ago
|
Comment 3•8 years ago
|
||
![]() |
||
Comment 4•8 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 10•8 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 16•8 years ago
|
||
Comment 17•8 years ago
|
||
Comment 18•8 years ago
|
||
Reporter | ||
Comment 19•8 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Comment 21•7 years ago
|
||
Updated•7 years ago
|
Updated•7 years ago
|
Assignee | ||
Comment 22•6 years ago
|
||
This patch should fix the test_ext_sendmessage_reply2.html intermittency which, based on the
timeout failure that I've been able to intermittently reproduce when running this test
locally using --verify, seems to be likely due to the following race:
the tabs.create API (used to create the extension tabs used as part of the tests) was called
right before subscribing the extension message listeners, and so from time to time the
extension tabs were not able to successfully send their messages to the background page listeners
(because the background page didn't subscribe the listeners yet) and as a result the test was getting
stuck waiting for extension messages that were never going to be received.
Assignee | ||
Updated•6 years ago
|
Comment 23•6 years ago
|
||
Comment 24•6 years ago
|
||
bugherder |
Assignee | ||
Comment 25•6 years ago
|
||
This test seems to be still failing intermittently, and its intermittency rate looks high enough.
Looking to the logs collected on the recent intermittent failures, it seems that the issue
is still related to the extension tabs opened in the test:
The two extension tabs (each one part of one of the two test extension) are going to exchange messages
between each other, and currently there is a chance (and apparently a very good chance) that one of the
two extension tabs is not yet ready to listen to the messages sent from the other extension tab.
This patch applies to the test the additional changes needed to ensure that both the extension tabs
are ready to exchange messages, before we let them exchange these messages over the extension messaging
API.
Comment 26•6 years ago
|
||
Comment 27•6 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment 29•6 years ago
|
||
This is still intermittently failing: https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=linux%2Cdebug%2Cmochitests%2Cwith%2Ce10s%2Ctest-linux32%2Fdebug-mochitest-e10s-15%2Cm-e10s%2815%29&fromchange=59b627e138589a04d58c93185f41ea4c65316770&tochange=37103bfa3dca5149f414cc6265d24fd752a4385f&selectedJob=224966411
The failure on the landed patch: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=224966411&repo=autoland&lineNumber=12820
Comment 30•6 years ago
|
||
There are 19 total failures in the last 7 days.
Luca can you please take another look at this?
Most recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=225342016&repo=mozilla-inbound&lineNumber=28138
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 32•6 years ago
|
||
(In reply to Andreea Pavel [:apavel] from comment #30)
There are 19 total failures in the last 7 days.
Luca can you please take another look at this?
Most recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=225342016&repo=mozilla-inbound&lineNumber=28138
Hi Andreea,
I was already keeping an eye on this test after we landed the first patch that has re-enabled it (linked in comment 24) and, as I mentioned in comment 25, I noticed that the test was still failing intermittently and its rate was clearly increasing and so I took care of it right away.
The patch attached in comment 25 has been already landed (comment 27) and looking at the failure we got since then:
- https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-01-27&endday=2019-02-03&tree=trunk&bug=1258897
- https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1258897&startday=2019-01-28&endday=2019-02-03&tree=all
the last patch seems to have been able to prevent further failures from being triggered (and the last hg revisions with a failure, the one linked in comment 30 and the last failure happened on try on Feb 2, do not include the changes from the last patch).
Assignee | ||
Updated•6 years ago
|
Comment 33•6 years ago
|
||
Luca, thanks for clarifying. I saw you landed the patch, however as Bogdan mentioned, there still was a failure on the push with your patch, thus I wanted to clarify this with you.
Looking in orange factor now, i see that there are no recent failures https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-01-29&endday=2019-02-05&tree=trunk&bug=1258897 so indeed this seems to be fixed.
Assignee | ||
Comment 34•6 years ago
|
||
Closing as fixed (as mentioned in Comment 32 and Comment 33 there are no further failure from this intermittent starting from Feb 2 2019)
Updated•6 years ago
|
Description
•