Closed
Bug 767820
Opened 13 years ago
Closed 13 years ago
Failure in testAboutPrivateBrowsing.js | Disconnect Error: Application unexpectedly closed
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(firefox13 fixed, firefox14 fixed, firefox15 fixed, firefox16 fixed, firefox-esr10 unaffected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox13 | --- | fixed |
firefox14 | --- | fixed |
firefox15 | --- | fixed |
firefox16 | --- | fixed |
firefox-esr10 | --- | unaffected |
People
(Reporter: u279076, Assigned: whimboo)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Attachments
(1 file)
3.96 KB,
patch
|
davehunt
:
review+
|
Details | Diff | Splinter Review |
Failure discovered while running 14.0b9 functional tests.
Module: /testPrivateBrowsing/testAboutPrivateBrowsing.js
Test: testCheckPrivateBrowsingMode
Error: Disconnect Error: Application unexpectedly closed
Report: http://mozmill-ci.blargon7.com/#/functional/report/44fc451c2e6b66b62172f2e13e17df77
status-firefox14:
--- → affected
Assignee | ||
Comment 1•13 years ago
|
||
This is Vista only. I will check that box if something is wrong with it. Regressed lately.
Anthony, please always put the link to the failure list into the URL field. Thanks.
Assignee: nobody → hskupin
Severity: normal → critical
Status: NEW → ASSIGNED
status-firefox13:
--- → affected
status-firefox15:
--- → affected
status-firefox16:
--- → affected
OS: All → Windows Vista
Assignee | ||
Comment 2•13 years ago
|
||
VM has been upgraded to the latest security fixes and restarted. Lets watch the results in the next couple of days.
Assignee | ||
Comment 3•13 years ago
|
||
The failure we are getting here in the log is:
Timeout: bridge.execFunction("d0f4258f-bf91-11e1-a14b-40a6d9fc6d3f", bridge.registry["{7efaa23f-f4eb-4bed-8cac-f9ea3a1a758f}"]["runTestFile"], ["c:\\users\\mozilla\\appdata\\local\\temp\\tmpmfsmn_.mozmill-tests\\tests\\functional\\testPrivateBrowsing\\testAboutPrivateBrowsing.js"])
TEST-UNEXPECTED-FAIL | Disconnect Error: Application unexpectedly closed
Timeout: bridge.set("f5b26d5e-bf91-11e1-a53e-40a6d9fc6d3f", Components.utils.import('resource://mozmill/modules/mozmill.js'))
I wasn't able to follow this testrun visually but it really looks like we crashed. I have to further investigate that.
Assignee | ||
Comment 4•13 years ago
|
||
As observed right now it doesn't look like that we crash but Firefox seems to freeze when loading the private browsing page on SUMO. The same happens for all the other tests we can see this disconnect.
This is the report:
http://mozmill-ci.blargon7.com/#/functional/report/faf11289b77273aad9ea281fc2018cfc
Assignee | ||
Comment 5•13 years ago
|
||
The page which gets loaded is:
http://support.mozilla.org/en-US/kb/private-browsing-browse-web-without-saving-info?redirectlocale=en-US&as=u&redirectslug=Private+Browsing
So probably we should change this test to use a local page instead.
Assignee | ||
Comment 6•13 years ago
|
||
Ok, so lets use a local page instead of the remote SUMO page. Works way fast now and hopefully should fix this problem.
Attachment #636713 -
Flags: review?(dave.hunt)
Comment 7•13 years ago
|
||
Comment on attachment 636713 [details] [diff] [review]
Patch v1
Looks great! Landed as:
http://hg.mozilla.org/qa/mozmill-tests/rev/c324742b67b1 (default)
Attachment #636713 -
Flags: review?(dave.hunt) → review+
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•13 years ago
|
||
Looks good today. No more failure in this test.
Pushed to other branches:
http://hg.mozilla.org/qa/mozmill-tests/rev/fba72f1ed3b7 (aurora)
http://hg.mozilla.org/qa/mozmill-tests/rev/70b6df6f45a4 (beta)
http://hg.mozilla.org/qa/mozmill-tests/rev/8319729d6978 (release)
Assignee | ||
Comment 9•13 years ago
|
||
This was fixed by just using a local page instead of one with a Flash object included. This would have been blocked by bug 770821.
Depends on: 770821
Assignee | ||
Updated•13 years ago
|
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
•