Closed Bug 1368778 Opened 7 years ago Closed 7 years ago

Intermittent test_navigation.py TestRefresh.test_refresh_in_child_frame_navigates_to_top | TimeoutException: Timed out after 6.9 seconds with message: No new tab has been opened

Categories

(Testing :: Marionette Client and Harness, defect)

Version 3
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: bulk-close-intermittents, intermittent-failure)

1496163913537	Marionette	TRACE	1073 -> [0,14,"clickElement",{"id":"250824b6-380c-414a-a138-b973ab0ac67b"}]
1496163913865	Marionette	TRACE	1073 <- [1,14,null,{}]
1496163913870	Marionette	TRACE	1073 -> [0,15,"getWindowHandles",{}]
1496163913875	Marionette	TRACE	1073 <- [1,15,null,["10737418677"]]
++DOCSHELL 0xd9cb5800 == 4 [pid = 1123] [id = {bc8c6a45-c940-43e3-b4eb-a7562f0c2a19}]
++DOMWINDOW == 29 (0xd9cb6400) [pid = 1123] [serial = 489] [outer = (nil)]
[Parent 924] WARNING: [nsFrameLoader] ReallyStartLoadingInternal tried but couldn't show remote browser.
: file /home/worker/workspace/build/src/dom/base/nsFrameLoader.cpp, line 785
++DOMWINDOW == 30 (0xd9dd9c00) [pid = 1123] [serial = 490] [outer = 0xd9cb6400]
1496163920697	Marionette	DEBUG	loaded listener.js
1496163920766	Marionette	TRACE	1073 -> [0,16,"getWindowHandles",{}]
1496163920776	Marionette	TRACE	1073 <- [1,16,null,["10737418677"]]

We are waiting 5s until the new tab should appear. As it looks like it doesn't happen here, and we timed out. Again, I don't know why there is just a huge gap between those two calls to `getWindowHandles`. Maybe it's related to the nsFrameLoader warning.

It sounds similar to the issue in bug 1368227.
See Also: → 1368227
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.