Closed
Bug 633959
Opened 13 years ago
Closed 13 years ago
Test failure in testTabRestoration.js | could not find element ID: history/localization
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aaronmt, Assigned: aaronmt)
References
()
Details
(Keywords: regression, Whiteboard: [mozmill-test-failure])
Attachments
(2 files)
1.05 KB,
patch
|
whimboo
:
review+
|
Details | Diff | Splinter Review |
1.13 KB,
patch
|
whimboo
:
review+
|
Details | Diff | Splinter Review |
Module: testTabRestoration.js Test: testTabRestoration Error: could not find element ID: history/localization Branch: default Platform: Windows 7 (NT 6.1.7600) http://hg.mozilla.org/qa/mozmill-tests/file/9d80953bf21c/firefox/testPrivateBrowsing/testTabRestoration.js#l98 http://mozmill-release.brasstacks.mozilla.com/#/general/failure?branch=4.0&platform=Windows%20NT&from=2011-02-07&to=2011-02-14&test=firefox%2FtestPrivateBrowsing%2FtestTabRestoration.js&func=testTabRestoration Also see bug 633944
Assignee | ||
Updated•13 years ago
|
Summary: Test failure in testTabRestoration | could not find element ID: history/localization → Test failure in testTabRestoration.js | could not find element ID: history/localization
Assignee | ||
Comment 1•13 years ago
|
||
It seems like on slower systems, we need to a waitForElement, looks like waitForPageLoad is insufficient on its own on exit of PB mode (is this needed with local pages?). Not sure again why this is exposed now all of a sudden, as well, only Windows 7. Inserting a waitForElement is giving me passes on qa-horus
Attachment #512288 -
Flags: review?(hskupin)
Comment 2•13 years ago
|
||
Comment on attachment 512288 [details] [diff] [review] Patch v1 - (default) [checked-in] Good catch! The underlying issue here is, that when leaving PB mode we load the pages from the bfcache. WaitForPageLoad cannot handle that at the moment. See the back and forward button test. Please land on all branches.
Attachment #512288 -
Flags: review?(hskupin) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Landed as: default - http://hg.mozilla.org/qa/mozmill-tests/rev/fa1542a55fe1 1.9.2 - http://hg.mozilla.org/qa/mozmill-tests/rev/937d0ba8cc0b 1.9.1 - http://hg.mozilla.org/qa/mozmill-tests/rev/6d3ed5c83bfa
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Attachment #512288 -
Attachment description: Patch v1 - (default) → Patch v1 - (default) [checked-in]
Assignee | ||
Comment 4•13 years ago
|
||
The new addition was placed in the wrong spot, but it was passing. It should really be in the spot after the exit of private browsing patch.
Attachment #512483 -
Flags: review?(hskupin)
Assignee | ||
Updated•13 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•13 years ago
|
Attachment #512483 -
Attachment description: Patch v2 - (default) → Patch v2 Follow-up correction - (default)
Updated•13 years ago
|
Attachment #512483 -
Flags: review?(hskupin) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Correction follow-up landed as: http://hg.mozilla.org/qa/mozmill-tests/rev/cb9858a4e815 http://hg.mozilla.org/qa/mozmill-tests/rev/fff0b8361416 http://hg.mozilla.org/qa/mozmill-tests/rev/b24479a1b338
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Attachment #512483 -
Attachment description: Patch v2 Follow-up correction - (default) → Patch v2 Follow-up correction - (default) [checked-in]
Updated•5 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
•