Intermittent dom/svg/test/test_non-scaling-stroke.html | single tracking bug
Categories
(Core :: SVG, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox131 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: longsonr)
References
Details
(Keywords: intermittent-failure, intermittent-testcase)
Attachments
(1 file)
Filed by: ctuns [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=422870893&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/aEEVOAijQx-rGq70J-zKfw/runs/0/artifacts/public/logs/live_backing.log
[task 2023-07-17T15:11:44.121Z] 15:11:44 INFO - TEST-START | dom/svg/test/test_non-scaling-stroke.html
[task 2023-07-17T15:11:44.199Z] 15:11:44 INFO - TEST-INFO | started process screenshot
[task 2023-07-17T15:11:44.326Z] 15:11:44 INFO - TEST-INFO | screenshot: exit 0
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - TEST-UNEXPECTED-FAIL | dom/svg/test/test_non-scaling-stroke.html | Testing mouse event on non-scaling-stroke click event fired - got false, expected true
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - SimpleTest.is@SimpleTest/SimpleTest.js:507:14
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - _checkExpectedEvent@SimpleTest/EventUtils.js:1768:7
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - synthesizeMouseExpectEvent@SimpleTest/EventUtils.js:1800:22
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - startTest/<@dom/svg/test/test_non-scaling-stroke.html?currentTestURL=dom%2Fsvg%2Ftest%2Ftest_non-scaling-stroke.html&closeWhenDone=1&showTestReport=false&expected=pass:38:35
[task 2023-07-17T15:11:44.329Z] 15:11:44 INFO - SimpleTest.waitForFocus/<@SimpleTest/SimpleTest.js:1056:13
[task 2023-07-17T15:11:44.330Z] 15:11:44 INFO - GECKO(2496) | MEMORY STAT | vsize 2103721MB | vsizeMaxContiguous 68570454MB | residentFast 84MB | heapAllocated 11MB
[task 2023-07-17T15:11:44.330Z] 15:11:44 INFO - TEST-OK | dom/svg/test/test_non-scaling-stroke.html | took 113ms
[task 2023-07-17T15:11:44.331Z] 15:11:44 INFO - GECKO(2496) | [Parent 6996, IPC I/O Parent] WARNING: DuplicateHandle failed for handle 0 in TransferHandles: file /builds/worker/checkouts/gecko/ipc/chromium/src/chrome/common/ipc_channel_win.cc:621
[task 2023-07-17T15:11:44.332Z] 15:11:44 INFO - GECKO(2496) | [GPU 2752, IPC I/O Child] WARNING: pipe error: 232: file /builds/worker/checkouts/gecko/ipc/chromium/src/chrome/common/ipc_channel_win.cc:443
[task 2023-07-17T15:11:44.332Z] 15:11:44 INFO - TEST-START | dom/svg/test/test_nonAnimStrings.xhtml
| Comment hidden (Intermittent Failures Robot) |
Comment 2•2 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Comment 3•1 year ago
|
||
This started failing on tier 1: https://treeherder.mozilla.org/logviewer?job_id=470252048&repo=mozilla-beta&lineNumber=13454 with this failure line: TEST-UNEXPECTED-FAIL | dom/svg/test/test_non-scaling-stroke.html | Test timed out. -
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
Comment 6•1 year ago
•
|
||
The screenshot from the recent failure log here in comment 3 is:
https://firefoxci.taskcluster-artifacts.net/VFnwWVr7Sa2qJEPe_xNxIQ/0/public/test_info/mozilla-test-fail-screenshot_q0yr4mtz.png
It shows that the system is showing the macOS screensaver, i.e. it looks like the system has become locked or we've triggered the screensaver timeout. This isn't the fault of this particular mochitest; presumably any test that requires focus will fail under these conditions.... Probably we need to adjust our CI stuff to make sure this doesn't happen?
Comment 7•1 year ago
|
||
jmaher do you know if/how we avoid triggering the screensaver shown in my screenshot linked in comment 6?
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 8•1 year ago
|
||
Comment 9•1 year ago
|
||
FWIW looking at the timeline in the log:, it looks like 28min elapsed (14:27 to 14:55) between the start of the log and the point at which the failing test was started (at which point the screensaver was presumably up):
[taskcluster 2024-08-13T14:27:48.881Z] Worker Type (releng-hardware/gecko-t-osx-1015-r8) settings:
[...]
[task 2024-08-13T14:55:44.730Z] 14:55:44 INFO - TEST-START | dom/svg/test/test_non-scaling-stroke.html
I'm not sure what the system screensaver timeout threshold is set to, but maybe it's on the order of 25-30min?
(And it looks like longsonr's link shows how to adjust it from the command line.)
Comment 10•1 year ago
|
||
The article from comment 8 suggests that we do:
defaults -currentHost write com.apple.screensaver idleTime 0
Looking in the log, I don't see us doing anything like that, which suggests maybe (?) we're just using Apple's default screensaver timeout. The closest thing that I see is this:
INFO - Running pre test command disable_dock with 'defaults write com.apple.dock autohide -bool true'
https://treeherder.mozilla.org/logviewer?job_id=470252048&repo=mozilla-beta&lineNumber=1157-1159
That seems to correspond to this in-tree:
https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/testing/mozharness/configs/unittests/mac_unittest.py#190-191
Maybe we should add a similar line there to set com.apple.screensaver idleTime?
Comment 11•1 year ago
•
|
||
(I'm a little curious why this hasn't been causing problems more often - my shot-in-the-dark guess is that usually we synthetically move the mouse often enough (in various tests towards the beginning and middle of each mochitest "bucket") to prevent the screensaver from ever triggering at least for the "buckets" of tests that include tests near the end that require focus and would fail if the screensaver had activated)
Comment 12•1 year ago
|
||
Comment 13•1 year ago
|
||
longsonr posted a patch to try to disable the screensaver in bug 1913448, fwiw. That should presumably avoid the failure that we hit in comment 3.
Comment 14•1 year ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 16•1 year ago
|
||
I think we can consider the root cause here fixed by bug 1913448.
Updated•1 year ago
|
| Comment hidden (Intermittent Failures Robot) |
Description
•