Closed
Bug 970226
Opened 10 years ago
Closed 7 years ago
Test failure 'controller.waitForPageLoad(): Timeout waiting for page loaded.' in /testPreferences/testSetToCurrentPage.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P4)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: andrei, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure][mozmill-test-skipped][blocked by bug 1015126])
Module: testSetHomePage Test: /testPreferences/testSetToCurrentPage.js Failure: controller.waitForPageLoad(): Timeout waiting for page loaded. Branches: mozilla-aurora Platforms: OSX http://mozmill-daily.blargon7.com/#/functional/report/e35f22a68fec3f6d144713f9ab013498 Failed only once. This is a local page. We don't expect to have this failures anymore with mozmill 2. Probably not relevant, but more info is always good. Note that child process closing down message received just before the test. > 02:07:01 TEST-END | testPreferences/testRestoreHomepageToDefault.js | finished in 2615ms > 02:07:01 NOTE: child process received `Goodbye', closing down > 02:07:01 TEST-START | testPreferences/testSetToCurrentPage.js | setupModule > 02:07:01 TEST-START | testPreferences/testSetToCurrentPage.js | testSetHomePage > 02:07:33 ERROR | Test Failure | { > 02:07:33 "exception": { > 02:07:33 "message": "controller.waitForPageLoad(): Timeout waiting for page loaded.", > 02:07:33 "lineNumber": 27, > 02:07:33 "name": "AssertionError", > 02:07:33 "fileName": "resource://mozmill/modules/errors.js" > 02:07:33 } > 02:07:33 } > 02:07:33 TEST-UNEXPECTED-FAIL | testPreferences/testSetToCurrentPage.js | testSetHomePage The only other instance of this message is after we have finished the whole testrun. Could some zombie processes make our http.js server misbehave?
Reporter | ||
Updated•10 years ago
|
status-firefox29:
--- → affected
Priority: -- → P4
Comment 1•10 years ago
|
||
Given that httpd.js is always running on the same port, it could be the case. But then not only this test should be affected.
Comment 2•9 years ago
|
||
It past a year and it didn't faild anymore, I'm closing it with WORKSFORME
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Comment 3•9 years ago
|
||
Please watch closely. This bug was skipped all the time along. No reason why there were no test failures. So fixing this is blocked on bug 1015126.
Status: RESOLVED → REOPENED
status-firefox29:
affected → ---
Depends on: 1015126
Resolution: WORKSFORME → ---
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped][blocked by bug 1015126]
Comment 4•7 years ago
|
||
Mozmill tests have been superseded by Marionette tests.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 7 years ago
Resolution: --- → INVALID
Updated•5 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
•