Closed
Bug 1055442
Opened 11 years ago
Closed 10 years ago
Test failure "Element.waitForElement(): Element 'ID: id" has been found' in /testTabbedBrowsing/testOpenInForeground.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P3)
Tracking
(firefox32 wontfix)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox32 | --- | wontfix |
People
(Reporter: andrei, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Module: testOpenInForegroundTab
Test: /testTabbedBrowsing/testOpenInForeground.js
Failure: Element.waitForElement(): Element 'ID: id'
Branches: mozilla-beta 32
Platforms: OSX
Locale: pl
Report: http://mozmill-release.blargon7.com/#/functional/report/2561af7d8c83a450772e8c438033c191
This failed exactly once, I am unable to reproduce it.
Comment 1•11 years ago
|
||
Failed again on Beta it - OSX 10.7:
http://mozmill-release.blargon7.com/#/functional/report/2f982f72826307fed840a3b11c436b37
status-firefox33:
--- → affected
| Reporter | ||
Comment 3•11 years ago
|
||
New failure:
http://mozmill-release.blargon7.com/#/functional/report/2f982f72826307fed840a3b11cd4e0f5
Interesting: all failures are on OSX 10.7.5
We total 9 failures in the last month.
Comment 4•11 years ago
|
||
Failed again twice with Beta 33 (et & is). Both failures on Mac OSX
http://mozmill-release.blargon7.com/#/functional/report/41b4fea479d86c7288732f3ea81a9a6d
http://mozmill-release.blargon7.com/#/functional/report/41b4fea479d86c7288732f3ea814b93b
Comment 5•11 years ago
|
||
Failed 4 times in this release:
http://mozmill-release.blargon7.com/#/functional/failure?app=Firefox&branch=All&platform=All&from=2014-10-01&to=&test=%2FtestTabbedBrowsing%2FtestOpenInForeground.js&func=testOpenInForegroundTab
Non-reproducible
| Reporter | ||
Comment 6•11 years ago
|
||
Still failing. Same MO. OSX 10.7.5, rare.
Example report for 34: http://mozmill-release.blargon7.com/#/functional/report/447e3274a76247e6567e1c2aa62dadee
status-firefox34:
--- → affected
| Reporter | ||
Comment 7•11 years ago
|
||
Some new info here. Same as bug 1066032 this only failed on mm-osx-107-2.
Comment 8•10 years ago
|
||
16 new failures since last update in this bug
Comment 9•10 years ago
|
||
The affected mm-osx-107-2 machine has been re-installed. This failure should no longer appear.
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox33:
affected → ---
status-firefox34:
affected → ---
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
This problem seems not to be fixed! :( Even a re-install caused the problem to appear again. Maybe we should put this machine offline again until we got this investigated.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 12•10 years ago
|
||
I took the machine offline again.
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
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
•