Closed
Bug 1117754
Opened 10 years ago
Closed 8 years ago
Test failure 'controller.waitForPageLoad(URI=about:newtab, readyState=uninitialized)' in testGeolocation/testAlwaysShareLocation.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(firefox34 unaffected, firefox35 unaffected, firefox36 affected, firefox37 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox34 | --- | unaffected |
firefox35 | --- | unaffected |
firefox36 | --- | affected |
firefox37 | --- | affected |
People
(Reporter: teodruta, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Module: setupTest
Test: testGeolocation/testAlwaysShareLocation.js
Failure: controller.waitForPageLoad(URI=about:newtab, readyState=uninitialized)
Branches: default, mozilla-aurora
Platforms: OS X
Locale: en-US
Report: http://mozmill-daily.blargon7.com/#/remote/report/5c7e7a22f9984b46554bc3b9fc2aa9f7
Comment 1•10 years ago
|
||
Which particular action triggers this page load? It would be good to mention that when filing such a bug in waitForPageLoad.
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #1)
> Which particular action triggers this page load? It would be good to mention
> that when filing such a bug in waitForPageLoad.
Most likely is the "*.tabBrowser.closeAllTabs();" line in setupTest. Closing all tabs opens a new 'about:newtab' tab, which apparently fails to load.
Comment 3•10 years ago
|
||
As the stack shows it is whatever is located at testAlwaysShareLocation.js:41:3:
http://hg.mozilla.org/qa/mozmill-tests/file/5e38750e19051923fc883e92dcb87843efd4d024/firefox/tests/remote/testGeolocation/testAlwaysShareLocation.js#l41
So yes, it is closeAllTabs. Given that it would be good if someone can go through all the open waitForPageLoad() bugs and check how many are failing in that method. We most likely can combine all of those bugs then.
Comment 4•8 years ago
|
||
Mozmill tests have been superseded by Marionette tests.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•