1812220 - Intermittent TV [tier 2] toolkit/components/printing/tests/browser_sheet_count.js | single tracking bug

Status: RESOLVED DUPLICATE of bug 1812236

(Toolkit :: Printing, defect, P5)

Description

[Treeherder Bug Filer]

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

---

[task 2023-01-25T00:28:22.489Z] 00:28:22     INFO - TEST-PASS | toolkit/components/printing/tests/browser_sheet_count.js | Preview Task is not armed - 
[task 2023-01-25T00:28:22.489Z] 00:28:22     INFO - Buffered messages logged at 00:28:22
[task 2023-01-25T00:28:22.489Z] 00:28:22     INFO - Leaving test bound testUpdateCopiesNoPreviewUpdate
[task 2023-01-25T00:28:22.490Z] 00:28:22     INFO - Buffered messages finished
[task 2023-01-25T00:28:22.490Z] 00:28:22     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/printing/tests/browser_sheet_count.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 2023-01-25T00:28:22.490Z] 00:28:22     INFO - GECKO(2299) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-01-25T00:28:22.491Z] 00:28:22     INFO - GECKO(2299) | MEMORY STAT | vsize 16053MB | residentFast 313MB | heapAllocated 130MB
[task 2023-01-25T00:28:22.491Z] 00:28:22     INFO - TEST-OK | toolkit/components/printing/tests/browser_sheet_count.js | took 58260ms

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:dholbert, since you are the author of the regressor, bug 1811970, could you take a look?

For more information, please visit auto_nag documentation.

Comment 2

[Daniel Holbert [:dholbert]]

Thanks for the heads-up! Fortunately, this isn't really anything to worry about.

My patch just removed a step from the test -- so any impact to the test duration should be to make it slightly faster.

The test-tweak triggered test-verify runs, just for this one push (as is standard for test-verify); and the test-verify run happened to exhibit a version of bug 1734020, where running many tests under chaos mode make them overshoot some timing thresholds.

Comment 3

[Daniel Holbert [:dholbert]]

oh, I guess 1734020 was filed as being WPT-specific; and we landed a patch for it to extend the timeout duration broadly for WPT tests under chaos mode, which is why that bug was fixed.

So: not strictly a dupe of that bug, but a version of the same basic issue (just in a different harness where we haven't sufficiently extended the timeout).

We need a "...for mochitests" version of that bug, I guess.