Closed Bug 594102 Opened 15 years ago Closed 15 years ago

Timeout failure in testAboutPrivateBrowsing.js (default)

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 593480

People

(Reporter: aaronmt, Assigned: aaronmt)

References

(
URL
)

Details

MODULE: firefox/testPrivateBrowsing/testAboutPrivateBrowsing.js TEST: testCheckPrivateBrowsingMode FAIL: controller.waitForEval: Timeout exceeded for 'subject.length == 2' BRANCH: default
Assignee: nobody → aaron.train
http://hg.mozilla.org/qa/mozmill-tests/file/2b2e393736ac/firefox/testPrivateBrowsing/testAboutPrivateBrowsing.js#l101 Getting mixed pass and fails running this test on trunk. Sometimes subject.length == 1 with the second tab opened. Henrik, I thought we fixed these race conditions and opening tabs in mozmill?
Now the other way around. Dupe of bug 593480.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Version: Trunk → unspecified
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.