Closed
Bug 862748
Opened 11 years ago
Closed 11 years ago
Test failure "Disconnect Error: Application unexpectedly closed" in /testFallbackUpdate/test3.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)
Tracking
(firefox20 affected, firefox21 affected, firefox22 affected, firefox23 affected, firefox24 affected, firefox26 affected, firefox27 affected)
People
(Reporter: mario.garbi, Unassigned)
References
Details
Attachments
(1 file)
284.17 KB,
image/png
|
Details |
Firefox 19.0 zh-TW on Win 6.2.9200 64bit View the build in Jenkins: http://mm-ci-master.qa.scl3.mozilla.com:8080/job/ondemand_update/7421/ View the results in the Mozmill Dashboard: http://mozmill-crowd.blargon7.com/#/update/report/8ec48e7ab0431a61b624e36d319645e5 http://mozmill-crowd.blargon7.com/#/update/report/8ec48e7ab0431a61b624e36d31965b8d
Reporter | ||
Updated•11 years ago
|
status-firefox20:
--- → affected
Comment 1•11 years ago
|
||
Failed again on Firefox 21.0 en-US: http://mozmill-ondemand.blargon7.com/#/update/report/49feb8c5f96a46e9037cffdde14627f1
status-firefox21:
--- → affected
Comment 2•11 years ago
|
||
Any other build can fail. This is not specific to en-US. I strongly believe it's the problem with the maintenance service which is opening a modal dialog during that step mentioning that the update could not be applied.
Priority: -- → P2
Happened again today on Windows 8 64-bit with Firefox 21.0b6 en-US: http://mozmill-ondemand.blargon7.com/#/update/report/452ec32f8deec0960aea87aa0667fb69
Comment 4•11 years ago
|
||
Happened again on Nightly IT on Windows 8 x86: http://mozmill-ci.blargon7.com/#/update/report/452ec32f8deec0960aea87aa06e1f52b
status-firefox23:
--- → affected
Comment 5•11 years ago
|
||
Happened on Nightly en-US with Windows 8 x86
status-firefox24:
--- → affected
Hardware: x86_64 → All
Comment 6•11 years ago
|
||
(In reply to Daniela Petrovici from comment #5) > Happened on Nightly en-US with Windows 8 x86 http://mozmill-ci.blargon7.com/#/update/report/8aa237803fd4b0e7348adc8bbec5dc44
Comment 7•11 years ago
|
||
Reproducible with Beta IT on Windows 8 x64: http://mozmill-ondemand.blargon7.com/#/update/report/f2d3b6136b11cb7b6708636cff2085ea Reproducible with Beta en-US on Windows 8 x86: http://mozmill-ondemand.blargon7.com/#/update/report/f2d3b6136b11cb7b6708636cff196c74
status-firefox22:
--- → affected
Comment 8•11 years ago
|
||
Happened on Windows 8 x64 with Nightly en-US http://mozmill-daily.blargon7.com/#/update/report/fb97b6210ae70da1b9ace6744594624b
Comment 9•11 years ago
|
||
Still failing, same machine as mentioned in comment 8, Win8, 64b, en-US: http://mozmill-daily.blargon7.com/#/update/report/1039ea48a9d69a5a1cc4fd228c4e4e9a
status-firefox26:
--- → affected
status-firefox27:
--- → affected
Comment 10•11 years ago
|
||
Most likely related to bug 918676.
Comment 11•11 years ago
|
||
Mario, have we seen any failures because of that in the last beta ondemand testruns over the last weekend (Sep 27-29)? If not this problem is fixed by bug 918676 and we might want to close this bug.
Flags: needinfo?(mario.garbi)
Reporter | ||
Comment 12•11 years ago
|
||
We had no failures to match this bug over the weekend. There were a few Disconnect Errors in test2 of testFallbackUpdate but those match Bug 808488 rather than this one. http://mozmill-ondemand.blargon7.com/#/update/report/6ec6776efe900da3fd2b64a7500632cd I will keep an eye out for other Disconnect Errors and close this if they don't happen again.
Flags: needinfo?(mario.garbi)
Comment 13•11 years ago
|
||
(In reply to mario garbi from comment #12) > We had no failures to match this bug over the weekend. There were a few > Disconnect Errors in test2 of testFallbackUpdate but those match Bug 808488 > rather than this one. No. That was because of bug 921598. We simply timed out. Not sure why we got a disconnect through. The next ondemand update tests will be run tomorrow. If none are failing with that disconnect, lets close the bug.
Reporter | ||
Comment 14•11 years ago
|
||
The most recent ondemand update runs have not failed with this so it's safe to close. If it happens again we can reopen it.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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
•