Closed Bug 1765067 Opened 3 years ago Closed 3 years ago

Intermittent docshell/test/chrome/test_bug321671.xhtml | Scroll position not restored while going back/forward! - got +0, expected 224

Categories

(Core :: DOM: Navigation, defect, P5)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1784831
Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox99 --- unaffected
firefox100 --- unaffected
firefox101 --- fix-optional

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [retriggered])

Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=374747520&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YjYGzosbThS-KqMQCD_54A/runs/0/artifacts/public/logs/live_backing.log

[task 2022-04-16T23:43:56.300Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | A pageshow event was expected for page bug321671 page3, but was fired for page bug321671 page3 
[task 2022-04-16T23:43:56.300Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | The persisted property of the pageshow event on page data:text/html,<html><head><title>bug321671 page3</title></head><body><table border='1' width='300' height='1000'><tbody><tr><td> page 3: foobar foobar foobar foobar </td></tr></tbody></table> </body></html> had an unexpected value 
[task 2022-04-16T23:43:56.301Z] 23:43:56     INFO - Buffered messages finished
[task 2022-04-16T23:43:56.301Z] 23:43:56     INFO - TEST-UNEXPECTED-FAIL | docshell/test/chrome/test_bug321671.xhtml | Scroll position not restored while going back! - got +0, expected 224
[task 2022-04-16T23:43:56.301Z] 23:43:56     INFO - SimpleTest.is@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:500:14
[task 2022-04-16T23:43:56.301Z] 23:43:56     INFO - runTest@chrome://mochitests/content/chrome/docshell/test/chrome/bug321671_window.xhtml:91:11
[task 2022-04-16T23:43:56.302Z] 23:43:56     INFO - GECKO(1581) | TEST: eventListener received a pagehide event for page bug321671 page3, persisted=true
[task 2022-04-16T23:43:56.302Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | A pagehide event was expected, but a pagehide event occurred 
[task 2022-04-16T23:43:56.302Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | originalTarget for last pagehide event not an HTMLDocument 
[task 2022-04-16T23:43:56.303Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | A pagehide event was expected for page bug321671 page3, but was fired for page bug321671 page3 
[task 2022-04-16T23:43:56.304Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | The persisted property of the pagehide event on page data:text/html,<html><head><title>bug321671 page3</title></head><body><table border='1' width='300' height='1000'><tbody><tr><td> page 3: foobar foobar foobar foobar </td></tr></tbody></table> </body></html> had an unexpected value 
[task 2022-04-16T23:43:56.304Z] 23:43:56     INFO - GECKO(1581) | TEST: eventListener received a pageshow event for page bug321671 page2, persisted=true
[task 2022-04-16T23:43:56.304Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | A pageshow event was expected, but a pageshow event occurred 
[task 2022-04-16T23:43:56.305Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | originalTarget for last pageshow event not an HTMLDocument 
[task 2022-04-16T23:43:56.305Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | A pageshow event was expected for page bug321671 page2, but was fired for page bug321671 page2 
[task 2022-04-16T23:43:56.306Z] 23:43:56     INFO - TEST-PASS | docshell/test/chrome/test_bug321671.xhtml | The persisted property of the pageshow event on page data:text/html,<html><head><title>bug321671 page2</title></head><body><table border='1' width='300' height='1000'><tbody><tr><td> page 2: foobar foobar foobar foobar </td></tr></tbody></table> </body></html> had an unexpected value 
[task 2022-04-16T23:43:56.306Z] 23:43:56     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-04-16T23:43:56.307Z] 23:43:56     INFO - TEST-UNEXPECTED-FAIL | docshell/test/chrome/test_bug321671.xhtml | Scroll position not restored while going back! - got +0, expected 192
[task 2022-04-16T23:43:56.307Z] 23:43:56     INFO - SimpleTest.is@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:500:14
[task 2022-04-16T23:43:56.307Z] 23:43:56     INFO - runTest@chrome://mochitests/content/chrome/docshell/test/chrome/bug321671_window.xhtml:91:11
[task 2022-04-16T23:43:56.307Z] 23:43:56     INFO - GECKO(1581) | TEST: eventListener received a pagehide event for page bug321671 page2, persisted=true

Daniel, could this be from the changes in Bug 1764902? retriggers here.

Flags: needinfo?(dholbert)

Nope, it couldn't -- the commit for Bug 1764902 has zero impact Nightly (or early beta for that matter). It added a build-time check to enable/disable a single line of code; the code continues was unconditionally enabled before that commit, and it's still enabled afterwards in builds that are configured as Nightly/Early-Beta (like the autoland builds that you're looking at here).

So: that commit is essentially a null change and has zero effect for builds on autoland and mozilla-central, and it's not possible for it to have caused a behavioral change.

Flags: needinfo?(dholbert)

Most likely, this would have been caused by Bug 1763598 (a few pushes before mine), this push here.

It made a bunch of changes to tests in the same directory as the failing test here. It didn't directly change the failing test itself, but the first commit[1] did make some changes to docshell_helpers.js[2] which this failing test does use[3].

I see we had a bunch of retriggers for this test run on that push, and none had failed yet; I spammed some more to test my theory. (It does look like it's relatively low frequency, on the order of less than 1 in 10 runs having a failure based on this later push. So it might take quite a few retriggers to get an orange.)

Looks like that push caused a regression in another test in the same directory, too (bug 1764997).

[1] https://hg.mozilla.org/integration/autoland/rev/3515b52d945ce3da4718e177dfd025a492e7cc3e
[2] https://searchfox.org/mozilla-central/source/docshell/test/chrome/docshell_helpers.js
[3] https://searchfox.org/mozilla-central/source/docshell/test/chrome/bug321671_window.xhtml#12

Flags: needinfo?(peterv)
Regressed by: 1763598

Set release status flags based on info from the regressing bug 1763598

status-firefox100: --- → unaffected
status-firefox101: --- → affected
status-firefox99: --- → unaffected
status-firefox-esr91: --- → unaffected
Has Regression Range: --- → yes
Summary: Intermittent docshell/test/chrome/test_bug321671.xhtml | Scroll position not restored while going back! - got +0, expected 224 → Intermittent docshell/test/chrome/test_bug321671.xhtml | Scroll position not restored while going back/forward! - got +0, expected 224
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(peterv)
You need to log in before you can comment on or make changes to this bug.