Closed Bug 1261495 Opened 8 years ago Closed 4 years ago

Intermittent browser_test_new_window_from_content.js | application timed out after 330 seconds with no output

Categories

(Core :: DOM: Core & HTML, defect, P5)

Product:
Core
Component:
DOM: Core & HTML
Version:
47 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

References

Details

(Keywords: intermittent-failure) 

I am going to re-enable this test except for Linux debug in bug 1262831 per 

https://bugzilla.mozilla.org/show_bug.cgi?id=1262831#c5: 

(In reply to Ryan VanderMeulen [:RyanVM] from comment #5)
> Looks like on Linux debug, browser_test_new_window_from_content.js is
> bumping right up against the per-test runtime limit and occasionally
> exceeding it (~130s with a max of 135s due requestLongerTimeout(3) already
> there). Non-e10s runs are closer to 70s in runtime. A ~2x regression seems
> pretty bad and worse than we'd typically expect. We could wallpaper over it
> by upping the timeout factor to 4, but it feels to me like the test could
> use someone looking at it a bit before that happens.
Definitely bolsters my thinking that this test is doing something screwy that warrants investigation :P
Flags: needinfo?(mconley)
I wonder if this is hitting the permitUnload timeout that (I believe) was causing TART failures on PGO builds (see bug 1253321). When the fix for that lands, we should see if this goes away.
Depends on: 1253321
Flags: needinfo?(mconley)
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Priority: P3 → P5
Component: DOM → DOM: Core & HTML

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.