Closed Bug 790218 Opened 9 years ago Closed 9 years ago

Mozmill test failure /testPopups/testPopupsAllowed.js | Disconnect Error: Application unexpectedly closed

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)

All
Windows 8
defect

Tracking

(firefox16 fixed, firefox17 fixed, firefox18 fixed)

RESOLVED FIXED
Tracking Status
firefox16 --- fixed
firefox17 --- fixed
firefox18 --- fixed

People

(Reporter: vladmaniac, Assigned: whimboo)

References

()

Details

(Whiteboard: [mozmill-test-failure])

Attachments

(1 obsolete file)

This started failing on Windows 8 both 32 and 64 bit versions
Error: Disconnect Error: Application unexpectedly closed
Mozmill version: 1.5.18
Firefox branch: default
Report link 64b: http://mozmill-ci.blargon7.com/#/functional/report/671677a5d9d5ca25f3cf5ae1c46e23c4
Report link 32b: http://mozmill-ci.blargon7.com/#/functional/report/671677a5d9d5ca25f3cf5ae1c46e29cb
Whiteboard: [mozmill-test-failure]
Lets see if other branches are also affected.
Priority: -- → P2
Priority: P2 → P1
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure] s=q3 u=failure c=bookmarks p=1
It is only happening on Windows 8.
So what's actually happens here is that we are stuck at "Transferring data from localhost..." in the add-on bar. This could be an issue with httpd.js on Windows 8 32/64. Jeff are you aware of anything like that?
Vlad, this is a critical failure so I want to see it at least fully investigated later today.
Severity: major → critical
Assignee: nobody → vlad.mozbugs
Status: NEW → ASSIGNED
IT is trying to set me up a Windows 8 VM on the test box. Stay tuned!
Well I have the win 8 env now but its so strange the disconnect is not reproducible for me. 
I'll have to dig in deeper, probably trigger some jobs again in jenkins.
Severity: critical → major
Status: ASSIGNED → NEW
Andreea or Alex, can one of you please take care of it ASAP until Vlad is back?
Severity: major → critical
So I nailed this down even a bit more. The problem on that bug is the following line in the testcase file:

http://mozqa.com/data/firefox/popups/popup_trigger.html?count=2

> window.open('popup_target.html', 'Test Popups ' + i, 'height=300,width=300');

Once it gets called loading of the page stops. It also happens with mozqa.com so it's definitely not a httpd.js issue.

Not sure why we end up with a disconnect here. It should at least run out of time in waitForPageLoad().

Loading the page outside of Mozmill works. So I would say it's an issue with Mozmill. I will file the bug once I found the real details.
So the underlying issue here is actually a bug in Firefox on Windows 8. I will file a bug soon.

The question why we do not run into a timeout for waitForPageLoaded() is still something I have to investigate and to fix in Mozmill.
Depends on: 791802
Depends on: 789773
No longer depends on: 791802
There is nothing we can do here. So I will pull this from the task list and replace it by another bug.
Assignee: vlad.mozbugs → nobody
Whiteboard: [mozmill-test-failure] s=q3 u=failure c=bookmarks p=1 → [mozmill-test-failure]
Depends on: 791960
Assignee: nobody → andreea.matei
Attached patch skip patch (obsolete) — Splinter Review
Skipping the test for Windows. It applies cleanly to aurora, beta and release too.
Attachment #662138 - Flags: review?(hskupin)
Attachment #662138 - Flags: review?(dave.hunt)
Comment on attachment 662138 [details] [diff] [review]
skip patch

Fixes have been landed on beta and aurora branches. For nightly it will follow soon. So I don't see a reason why we have to skip those patches now.
Attachment #662138 - Attachment is obsolete: true
Attachment #662138 - Flags: review?(hskupin)
Attachment #662138 - Flags: review?(dave.hunt)
With the fix on bug 789773 landed on all the affected branches, the failure is gone now. Yay! We have a clean testrun on Windows 8 now.
Assignee: andreea.matei → hskupin
Status: NEW → RESOLVED
Closed: 9 years ago
No longer depends on: 791960
Resolution: --- → FIXED
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #15)
> I'm not sure why but it appears this has come back for Firefox 25.0a2:
> http://mozmill-daily.blargon7.com/#/functional/failure?branch=25.
> 0&platform=Windows%20NT&from=2013-08-04&to=2013-09-
> 16&test=%2FtestPopups%2FtestPopupsAllowed.js&func=teardownModule

I think this is more than likely bug 898194
That's correct, the recent failures were fallouts from bug 898194
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.