Intermittent in browser_history_persist.js (wrong URL: got about:blank, should be about:robots) in fission
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox85 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | disabled |
firefox88 | --- | disabled |
firefox89 | --- | disabled |
firefox90 | --- | fixed |
People
(Reporter: jesup, Assigned: u608768)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Bug 1673617 causes a new intermittent in fission only, where the URL is incorrect occasionally (~30% on Try, <1% locally).
TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_history_persist.js | Should be the right URL - Got "about:blank", expected "about:robots"
often but not always followed by:
TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_history_persist.js | Should be two history entries - Got 1, expected 2
TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_history_persist.js | Uncaught exception - [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsISHistory.getEntryAtIndex]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_history_persist.js :: check_history_default_persisted :: line 155" data: no]
TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_history_persist.js | Found an unexpected tab at the end of test run: about:blank -
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Set release status flags based on info from the regressing bug 1673617
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Tracking for Fission M7 for re-enabling this test.
[browser_history_persist.js]
skip-if = fission # Bug 1690134
Updated•4 years ago
|
Updated•4 years ago
|
Comment 3•4 years ago
|
||
I'm taking a look at this, though I'm not familiar with session store.
Comment 4•4 years ago
|
||
It sounds like this might be fixed by Kashav and Andreas's work on session restore, so I'll assign it to Kashav for enabling.
Will enable this in bug 1597499.
Happening again, particularly often with the patches from bug 1702055. I think I have a fix.
Waiting for the about:robots load explicitly ensures we don't proceed until all
history changes have fully propagated.
Updated•4 years ago
|
Comment 9•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•