Closed
Bug 1066032
Opened 11 years ago
Closed 11 years ago
Test failure 'controller(): Window has been initialized' in /testSecurity/testSubmitUnencryptedInfoWarning.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P3)
Tracking
(firefox35 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox35 | --- | affected |
People
(Reporter: cosmin-malutan, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Module: lib/modal-dialog.js:94
Test: testSubmitUnencryptedInfoWarning
Failure: 'controller(): Window has been initialized'
Branches: aurora
Platforms: OSX
http://mozmill-daily.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-09-11&to=&test=%2FtestSecurity%2FtestSubmitUnencryptedInfoWarning.js&func=testSubmitUnencryptedInfoWarning
| Reporter | ||
Comment 1•11 years ago
|
||
I rebuilded it, it didn't reproduce.
Updated•11 years ago
|
Priority: -- → P4
Comment 2•11 years ago
|
||
http://mozmill-release.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-09-11&test=%2FtestSecurity%2FtestSubmitUnencryptedInfoWarning.js&func=testSubmitUnencryptedInfoWarning
Al recorded failures are on OSX 10.7.5 (total 5 of them since Sept 11th, none recorded before that)
Comment 3•11 years ago
|
||
Failed 2 times yesterday on Mac OS X 10.7.5 with different locales.
Comment 4•11 years ago
|
||
4 failures today again.
Comment 5•11 years ago
|
||
Still failing. Only OSX 10.7.5 affected.
23 failures in the last month.
Priority: P4 → P3
Is this across 10.7.5 machines or a specific one?
Comment 7•11 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #6)
> Is this across 10.7.5 machines or a specific one?
Good question. All are on mm-osx-107-2!
I will take the machine offline.
We have another issue which is "OSX only, and only on 10.7" I will find it and check whether its the same machine.
Since mm-osx-107-2 has been re-installed this failure should be gone.
Status: NEW → RESOLVED
Closed: 11 years ago
status-firefox32:
affected → ---
status-firefox33:
affected → ---
status-firefox34:
affected → ---
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
The failure still reproduces on that machine. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•11 years ago
|
||
status-firefox35:
--- → affected
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•7 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
•