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)

All
macOS
defect

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.
Actually it failed 5 times today. Raising priority a bit.
Priority: P4 → P3
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.
Still failing. Same MO. OSX 10.7.5, rare. Example report for 34: http://mozmill-release.blargon7.com/#/functional/report/447e3274a76247e6567e1c2aa62dadee
Some new info here. Same as bug 1066032 this only failed on mm-osx-107-2.
Depends on: 1087261
16 new failures since last update in this bug
The affected mm-osx-107-2 machine has been re-installed. This failure should no longer appear.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
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 → ---
I took the machine offline again.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.