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

Status: RESOLVED FIXED

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

Description

[Treeherder Bug Filer]

Filed by: hskupin [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=149529881&repo=try

https://queue.taskcluster.net/v1/task/L0EeTW9pT3-m8nDrMN7j5g/runs/0/artifacts/public/logs/live_backing.log

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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.

Comment 3

[Intermittent Failures Robot]

41 failures in 178 pushes (0.23 failures/push) were associated with this bug yesterday.    

Repository breakdown:
* autoland: 31
* mozilla-central: 8
* mozilla-inbound: 2

Platform breakdown:
* osx-10-10: 12
* linux64: 12
* windows7-32: 11
* windows10-64: 4
* linux32: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1422741&startday=2017-12-05&endday=2017-12-05&tree=all

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: 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.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Removing needinfo based that it should have been set for bug 1422769.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: Bug 1422741 - Skip test_strategy_after_remoteness_change for intermittent failures.

Review commit: https://reviewboard.mozilla.org/r/205832/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/205832/

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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 8

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Comment on attachment 8934905 [details]
Bug 1422741 - Skip test_strategy_after_remoteness_change for intermittent failures.

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/205832/diff/1-2/

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 10

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d9751a1b5dbb
Skip test_strategy_after_remoteness_change for intermittent failures. r=whimboo

Comment 11

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/d9751a1b5dbb

Comment 12

[Intermittent Failures Robot]

61 failures in 157 pushes (0.389 failures/push) were associated with this bug yesterday.    

Repository breakdown:
* mozilla-inbound: 27
* autoland: 18
* mozilla-central: 11
* try: 5

Platform breakdown:
* osx-10-10: 20
* windows7-32: 15
* linux64: 12
* windows10-64: 6
* linux32: 6
* windows10-64-ccov: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1422741&startday=2017-12-06&endday=2017-12-06&tree=all

Comment 13

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This was just a skip patch. The bug has to stay open until we can re-enable the test.

Comment 14

[Intermittent Failures Robot]

124 failures in 889 pushes (0.139 failures/push) were associated with this bug in the last 7 days. 

This is the #7 most frequent failure this week. 

** This failure happened more than 75 times this week! Resolving this bug is a very high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 1 week, the affected test(s) may be disabled. **   

Repository breakdown:
* autoland: 59
* mozilla-inbound: 30
* mozilla-central: 21
* try: 14

Platform breakdown:
* osx-10-10: 36
* linux64: 32
* windows7-32: 30
* windows10-64: 12
* linux32: 11
* windows10-64-ccov: 2
* linux64-ccov: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1422741&startday=2017-12-04&endday=2017-12-10&tree=all

Comment 15

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup

Comment 16

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 17

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 18

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 19

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: Bug 1422741 - [marionette] Re-enable test TestPageLoadStrategy.test_strategy_after_remoteness_change. r?ato

Comment 20

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/00b712b8f283
[marionette] Re-enable test TestPageLoadStrategy.test_strategy_after_remoteness_change. r=ato

Comment 21

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/00b712b8f283

Comment 22

[BMO Automation]

Moving bug to Testing::Marionette Client and Harness component per bug 1815831.