Closed Bug 1422741 Opened 7 years ago Closed 5 years ago

Intermittent test_navigation.py TestRefresh.test_basic | NoSuchElementException: Failed to trigger opening a new tab: Web element reference not seen before

Categories

(Testing :: Marionette Client and Harness, defect, P2)

Product:
Testing
Component:
Marionette Client and Harness
Version:
Version 3
Type:
defect

Tracking

(firefox59 disabled, firefox64 disabled, firefox65 disabled, firefox66 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla66
Tracking Flags:
Tracking Status
firefox59 --- disabled
firefox64 --- disabled
firefox65 --- disabled
firefox66 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: whimboo)

References

Details

(Keywords: intermittent-failure)

Attachments

(3 files)

screenshot.png
17.05 KB, image/png
Details
Bug 1422741 - Skip test_strategy_after_remoteness_change for intermittent failures.
59 bytes, text/x-review-board-request
whimboo
: review+
Details
Bug 1422741 - [marionette] Re-enable test TestPageLoadStrategy.test_strategy_after_remoteness_change. r?ato
47 bytes, text/x-phabricator-request
Details | Review
Component: JSMarionette → Marionette
05:21:34     INFO - TEST-UNEXPECTED-ERROR | testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py TestRefresh.test_basic | NoSuchElementException: Failed to trigger opening a new tab: Web element reference not seen before: a7f272a2-2889-d04a-8d62-efe1b81a942a
05:21:34     INFO - stacktrace:
05:21:34     INFO - 	WebDriverError@chrome://marionette/content/error.js:172:5
05:21:34     INFO - 	NoSuchElementError@chrome://marionette/content/error.js:400:5
05:21:34     INFO - 	get@chrome://marionette/content/element.js:231:13
05:21:34     INFO - 	clickElement@chrome://marionette/content/listener.js:1318:14
05:21:34     INFO - Traceback (most recent call last):
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_harness/marionette_test/testcases.py", line 141, in run
05:21:34     INFO -     self.setUp()
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/tests/marionette/tests/testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py", line 53, in setUp
05:21:34     INFO -     self.new_tab = self.open_tab(open_with_link)
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_harness/runner/mixins/window_manager.py", line 65, in open_tab
05:21:34     INFO -     trigger()
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/tests/marionette/tests/testing/marionette/harness/marionette_harness/tests/unit/test_navigation.py", line 49, in open_with_link
05:21:34     INFO -     link.click()
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_driver/marionette.py", line 85, in click
05:21:34     INFO -     self.marionette._send_message("clickElement", {"id": self.id})
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_driver/decorators.py", line 23, in _
05:21:34     INFO -     return func(*args, **kwargs)
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_driver/marionette.py", line 740, in _send_message
05:21:34     INFO -     self._handle_error(err)
05:21:34     INFO -   File "/Users/cltbld/tasks/task_1512391240/build/venv/lib/python2.7/site-packages/marionette_driver/marionette.py", line 764, in _handle_error
05:21:34     INFO -     raise errors.lookup(error)(message, stacktrace=stacktrace)
05:21:34     INFO - TEST-INFO took 1438ms


The problem happens here:

>        self.marionette.navigate(self.marionette.absolute_url("windowHandles.html"))
>    --> self.new_tab = self.open_tab(open_with_link)

In `open_tab` a click on an element is performed which should be immediately present when the loading of "windowHandles.html" has been done.

05:21:34     INFO -  [Parent 1750, Main Thread] WARNING: [nsFrameLoader] ReallyStartLoadingInternal tried but couldn't show remote browser.
05:21:34     INFO -  : file /builds/worker/workspace/build/src/dom/base/nsFrameLoader.cpp, line 904

This looks similar to bug 1418696. I will file a new dependency for all.
Depends on: 1422769
This failure happens a lot today for debug builds across platforms. I'm not sure what triggers it, nor that I can reproduce locally or via a one-click loaner.
Attached image screenshot.png — 
This screenshot shows that we do not load the browser at all for the requested page.

Mike, can you help us to understand this problem? It kinda looks like a bug in Firefox:

16:48:06     INFO -  [Parent 624, Main Thread] WARNING: [nsFrameLoader] ReallyStartLoadingInternal tried but couldn't show remote browser.
16:48:06     INFO -  : file /builds/worker/workspace/build/src/dom/base/nsFrameLoader.cpp, line 904

Thanks.
Flags: needinfo?(mconley)
Priority: P5 → P2
Removing needinfo based that it should have been set for bug 1422769.
Flags: needinfo?(mconley)
Skipping just this test doesn't help, because the next on in the series is affected. So I get the feeling that something is wrong with the test run before which is test_strategy_after_remoteness_change. I will do a try push with a skip for that one.
Comment on attachment 8934905 [details]
Bug 1422741 - Skip test_strategy_after_remoteness_change for intermittent failures.

https://reviewboard.mozilla.org/r/205832/#review211420

r=me for disabling the problematic test
Attachment #8934905 - Flags: review+
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d9751a1b5dbb
Skip test_strategy_after_remoteness_change for intermittent failures. r=whimboo
https://hg.mozilla.org/mozilla-central/rev/d9751a1b5dbb
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox59: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Assignee: nobody → hskupin
This was just a skip patch. The bug has to stay open until we can re-enable the test.
Assignee: hskupin → nobody
Status: RESOLVED → REOPENED
status-firefox59: fixed → disabled
Keywords: test-disabled
Resolution: FIXED → ---
Target Milestone: mozilla59 → ---
Whiteboard: [stockwell disabled]
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → INCOMPLETE

The causing test is still disabled, and as such no more failures occurred here.

Status: RESOLVED → REOPENED
status-firefox64: --- → disabled
status-firefox65: --- → disabled
status-firefox66: --- → disabled
Keywords: leave-open
Resolution: INCOMPLETE → ---

The problems I faced with multiple content processes seem to be gone. Also I cannot reproduce this test failure anymore when running the navigation tests in a loop locally. Lets try if we can get the test test_strategy_after_remoteness_change re-enabled:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=c9341187b15b92c4d7b232914b1b0f924d847432

The try build looks indeed fine. I will upload a patch.

Assignee: nobody → hskupin
Status: REOPENED → ASSIGNED
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/00b712b8f283
[marionette] Re-enable test TestPageLoadStrategy.test_strategy_after_remoteness_change. r=ato
Status: ASSIGNED → RESOLVED
Closed: 6 years ago → 5 years ago
status-firefox66: disabled → fixed
Keywords: leave-open, test-disabled
Resolution: --- → FIXED
Whiteboard: [stockwell disabled]
Target Milestone: --- → mozilla66
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.

Attachment

General

Creator:
Created:
Updated:
Size: