Closed Bug 1860705 Opened 2 years ago Closed 2 years ago

Intermittent [TV] accessible/tests/mochitest/events/test_statechange.html | single tracking bug

Categories

(Core :: Disability Access APIs, defect, P5)

defect

Tracking

()

RESOLVED FIXED
123 Branch
Tracking Status
firefox123 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: dholbert)

References

Details

(Keywords: intermittent-failure, test-verify-fail)

Attachments

(1 file)

Filed by: smolnar [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=433518417&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/FE7FFh4NRjW9f39pOjUZPg/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/FE7FFh4NRjW9f39pOjUZPg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


TEST-OK | accessible/tests/mochitest/events/test_statechange.html | took 2618ms
[task 2023-10-24T00:20:50.114Z] 00:20:50    ERROR - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/tests/mochitest/events/test_statechange.html | changed preference: security.mixed_content.upgrade_display_content
[task 2023-10-24T00:20:50.114Z] 00:20:50     INFO - TEST-START | Shutdown
Summary: Intermittent [TV] accessible/tests/mochitest/events/test_statechange.html | changed preference: security.mixed_content.upgrade_display_content → Intermittent [TV] accessible/tests/mochitest/events/test_statechange.html | single tracking bug

:Jamie, since you are the author of the regressor, bug 1661923, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(jteh)

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

bug 1661923 didn't "regress" this (and this isn't an intermittent). bug 1661923 just happened to touch this test and trigger a test-verify run, which revealed this as a preexisting issue with this test.

The preexisting issue here is that this test sets a pref without ever unsetting it (and test-verify checks for that). That pref-tweak is here:
https://searchfox.org/mozilla-central/rev/9c509b8feb28c1e76ad41e65bf9fd87ef672b00f/accessible/tests/mochitest/events/test_statechange.html#21-24

// Disable mixed-content upgrading as this test is expecting an HTTP load
Services.prefs.setBoolPref(
  "security.mixed_content.upgrade_display_content",
  false

This test should probably use one of the pushPref APIs that automatically revert the pref-modification when the test completes.

Keywords: regression
No longer regressed by: 1661923

(clearing affected version flags which were improperly inferred from the supposed-regressor.)

That setBoolPref invocation came from this commit:
https://hg.mozilla.org/mozilla-central/rev/042aa9ec5d10

(That commit added one other setBoolPref call for the same pref in a different test, and it looks like we already fixed that one over in bug 1866585.)

Depends on: 1550792

setBoolPref has a persistent effect for the rest of the test run (potentially
affecting the behavior of other prefs), so we don't want to use
that. This test is currently failing when run in test-verify mode as a result
of this. With pushPrefEnv, the test will properly undo its pref-modification
when it completes.

Note: I'm moving the pref-toggle statement inside of a function so that I can
use the ergonomic await syntax. This is still essentially right at the start
of the test, since doTests is the main function here.

Assignee: nobody → dholbert
Status: NEW → ASSIGNED
Pushed by dholbert@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/49f61b86d1b7 Use pushPrefEnv instead of setBoolPref in mochitest test_statechange.html. r=eeejay
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
Flags: needinfo?(jteh)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: