Open
Bug 1237758
Opened 9 years ago
Updated 2 years ago
Intermittent test_browserElement_NotifyChannel.html | Test timed out
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: philor, Unassigned)
References
Details
(Keywords: intermittent-failure)
Comment 1•9 years ago
|
||
Ken, this test failure apparently is happening pretty consistently too. Can you help us find an owner here?
Flags: needinfo?(kchang)
Comment 2•9 years ago
|
||
Edgar, can you please look into this bug?
Flags: needinfo?(kchang) → needinfo?(echen)
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 6•9 years ago
|
||
Alastor, this test case is added by you, can you please look into this bug?
Flags: needinfo?(echen) → needinfo?(alwu)
Updated•9 years ago
|
Assignee: nobody → alwu
Flags: needinfo?(alwu)
Comment 7•9 years ago
|
||
Hi, baku,
Could you help me take a look about this issue?
It's resulted by the iframe can't be loading successfully, then the test case timeout.
I can't reproduce it on my local environment, and I have encountered the same problem before, and my solution was just to change the order of the these two lines.
> document.body.appendChild(iframe) and iframe.addEventListener(...)
Therefore, I am guessing there might be something wrong in the DOM iframe loading process.
Very appreciate!
Flags: needinfo?(amarchesini)
Comment hidden (Intermittent Failures Robot) |
Comment 9•9 years ago
|
||
Alastor, as far as I can tell this test already places the addEventListener() before appendChild(). Are you sure this is the issue at work here?
Flags: needinfo?(alwu)
Comment 10•9 years ago
|
||
I was looking at the code here:
https://dxr.mozilla.org/mozilla-central/source/dom/browser-element/mochitest/browserElement_NotifyChannel.js#105
Comment 11•9 years ago
|
||
Hi, Ben,
First time I saw this problem was I did some test for bug1223297, because that test might cause time-out, then I did the solution mentioned in comment 7. Magically, it worked, but I still didn't know what happened.
What I guessed is that it might be related with the previous test, if the previous test didn't remove its frame, then this issue have possibility to fail.
Recently, I also have some test cases timeout are similar with this bug, all of them can't receive the "mozbrowserloadend" event correctly. See bug1238470 and bug1238472. I also notice something that the previous test cases in those bugs don't remove its iframe after the test case ended.
Therefore, I think the problem still exists.
Flags: needinfo?(alwu)
Comment hidden (Intermittent Failures Robot) |
Comment 13•9 years ago
|
||
Kan-Ru, can you help investigate this top orange? I was told you might be the right person for mozbrowser load issues.
Flags: needinfo?(kchen)
Comment 14•9 years ago
|
||
I'll take a look as soon as possible.
Assignee: alwu → kchen
Flags: needinfo?(kchen)
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) |
Updated•9 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) |
Updated•9 years ago
|
Flags: needinfo?(amarchesini)
Updated•9 years ago
|
Assignee: kchen → nobody
Comment 27•8 years ago
|
||
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Updated•7 years ago
|
Priority: P3 → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•