Open Bug 1923539 Opened 1 year ago Updated 3 days ago

Intermittent browser/components/preferences/tests/browser_moreFromMozilla.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -

Categories

(Firefox :: Settings UI, defect, P5)

Product:
Firefox
Component:
Settings UI
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr128 --- unaffected
firefox131 --- unaffected
firefox132 --- unaffected
firefox133 --- affected
firefox134 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

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

Filed by: tszentpeteri [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=477388853&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZrD2DRo2SZiVq7YPV9gRhQ/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/ZrD2DRo2SZiVq7YPV9gRhQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

[task 2024-10-09T00:12:38.318Z] 00:12:38     INFO - TEST-PASS | browser/components/preferences/tests/browser_moreFromMozilla.js | URL matched - "https://relay.firefox.com/?utm_source=about-prefs&utm_campaign=morefrommozilla&utm_medium=firefox-desktop&utm_content=fxvt-113-a-global&entrypoint_experiment=morefrommozilla-experiment-1846&entrypoint_variation=treatment-simple" == "https://relay.firefox.com/?utm_source=about-prefs&utm_campaign=morefrommozilla&utm_medium=firefox-desktop&utm_content=fxvt-113-a-global&entrypoint_experiment=morefrommozilla-experiment-1846&entrypoint_variation=treatment-simple" - 
[task 2024-10-09T00:12:38.319Z] 00:12:38     INFO - Leaving test bound test_aboutpreferences_clickBtnRelay
[task 2024-10-09T00:12:38.319Z] 00:12:38     INFO - Buffered messages finished
[task 2024-10-09T00:12:38.320Z] 00:12:38     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_moreFromMozilla.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2024-10-09T00:12:38.320Z] 00:12:38     INFO - GECKO(4818) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2024-10-09T00:12:38.321Z] 00:12:38     INFO - GECKO(4818) | MEMORY STAT | vsize 16725MB | residentFast 416MB | heapAllocated 199MB
[task 2024-10-09T00:12:38.321Z] 00:12:38     INFO - TEST-OK | browser/components/preferences/tests/browser_moreFromMozilla.js | took 89955ms
[task 2024-10-09T00:12:38.322Z] 00:12:38     INFO - checking window state
[task 2024-10-09T00:12:38.322Z] 00:12:38     INFO - GECKO(4818) | Completed ShutdownLeaks collections in process 4818
[task 2024-10-09T00:12:38.323Z] 00:12:38     INFO - TEST-START | Shutdown

:chutten, since you are the author of the regressor, bug 1920562, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(chutten)

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

status-firefox131: --- → unaffected
status-firefox132: --- → unaffected
status-firefox133: --- → affected
status-firefox-esr128: --- → unaffected

bug 1920562's change to this test is not one that would change how long the test takes to run. It just removed a Services.telemetry.setEventRecordingEnabled call.

I'm not ruling out side-effects of other aspects of the change (e.g. maybe clearEvents takes longer now?), though, so I'll take a look.

Assignee: nobody → chutten
Status: NEW → ASSIGNED
Flags: needinfo?(chutten)

I wonder if there's something weird about macosx1015-64-qr because it times out at 90s but linux1804-64-qr shows runs coming in at 43-50s.

Weird, earlier macosx1015-64-qr TV runs are single-job (TV, as opposed to my failing run which has TV1-TV3). Maybe the task config changed?

Looking at the log, it takes 14s to get from the start of the test bound of testDefaultUIWithoutTemplatePref to the first assert ("The category exists")... fourteen whole seconds to go 11 lines seems like a lot. And from there it takes ages to do anything at all. And it times out about 3/4 of the way through the file.

Wow, it just is really slow. Really, really slow.

And without previous jobs to compare it to, I don't know how fast it's supposed to go. And then there's bug 1923538 which times out a different test in the same group, which makes me wonder if maybe everything is just really really slow... and it came in before my change.

I don't know that this had ought to do with my change.

Assignee: chutten → nobody
Status: ASSIGNED → NEW

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

status-firefox134: --- → affected
Summary: Intermittent [TV] browser/components/preferences/tests/browser_moreFromMozilla.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - → Intermittent browser/components/preferences/tests/browser_moreFromMozilla.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
You need to log in before you can comment on or make changes to this bug.