Closed Bug 1032062 Opened 11 years ago Closed 11 years ago

Test failure 'Final wizard page has been selected.' in /testFallbackUpdate/test3.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(firefox33 affected)

RESOLVED DUPLICATE of bug 972912
Tracking Status
firefox33 --- affected

People

(Reporter: andrei, Unassigned)

References

()

Details

(Whiteboard: [mozmill-test-failure])

Module: testFallbackUpdate_ErrorPatching Test: /testFallbackUpdate/test3.js Failure: Final wizard page has been selected. Branches: BRANCH Report: http://mozmill-release.blargon7.com/#/update/report/883d8406dab55a771a00934158ded23d There's a high change this is actually bug 816470. That was supposed to be fixed. I can't be sure that the underlying cause is the same because of bug 1008135, so we don't have the update log available.
Well, what is the Jenkins job #? The HTTP log attached there should give this information too.
Oh, well this is the http log: http://mm-ci-master.qa.scl3.mozilla.com:8080/job/ondemand_update/76828/artifact/http.log I'm not sure I'm able to make out any of it. Instead of downloading more than its supposed to (as was the case in bug 816470), this looks as if the download stopped early. Then again, I don't have a good grasp of this low-level log. I might have read it completely backwards...
Yeah, it's very hard those days to get something out of it. Anyway, lets try to finish the dependency the next days so that we have this output again.
This test failed today with the 31.0 update tests on beta for Firefox 29.0 (29.0, kn, 20140417185217): http://mozmill-release.blargon7.com/#/update/report/a3b8d1e9bea5a0fc05cd41dbf64e9378 test4.js also failed. Does that need a separate bug?
Lix, in this report I don't see test1.js being ran at all, so this must be bug 972912.
Indeed. Even the initially reported failure is showing this problem.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.