Closed Bug 1819768 Opened 3 years ago Closed 2 years ago

Intermittent dom/security/test/https-only/browser_httpsonly_speculative_connect.js | single tracking bug

Categories

(Testing :: Mochitest, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, intermittent-testcase, Whiteboard: [domsecurity-intermittent])

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


[task 2023-03-01T20:55:35.870Z] 20:55:35     INFO - TEST-PASS | dom/security/test/https-only/browser_httpsonly_speculative_connect.js | Upgrade should get logged - 
[task 2023-03-01T20:55:35.870Z] 20:55:35     INFO - Leaving test bound 
[task 2023-03-01T20:55:35.871Z] 20:55:35     INFO - Buffered messages finished
[task 2023-03-01T20:55:35.872Z] 20:55:35     INFO - TEST-UNEXPECTED-FAIL | dom/security/test/https-only/browser_httpsonly_speculative_connect.js | waiting for vsync to be disabled - timed out after 50 tries. - false == true - {"filename":"chrome://mochikit/content/browser-test.js","name":"ensureVsyncDisabled","sourceId":530,"lineNumber":587,"columnNumber":19,"sourceLine":"","asyncCause":null,"asyncCaller":null,"caller":null,"formattedStack":"ensureVsyncDisabled@chrome://mochikit/content/browser-test.js:587:19\n","nativeSavedFrame":{}}
[task 2023-03-01T20:55:35.872Z] 20:55:35     INFO - Stack trace:
[task 2023-03-01T20:55:35.872Z] 20:55:35     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:587
[task 2023-03-01T20:55:35.872Z] 20:55:35     INFO - Not taking screenshot here: see the one that was previously logged
[task 2023-03-01T20:55:35.873Z] 20:55:35     INFO - TEST-UNEXPECTED-FAIL | dom/security/test/https-only/browser_httpsonly_speculative_connect.js | vsync remained enabled at the end of the test. Is there an animation still running? Consider talking to the performance team for tips to solve this. - false == true - {"filename":"chrome://mochikit/content/browser-test.js","name":"ensureVsyncDisabled","sourceId":530,"lineNumber":588,"columnNumber":19,"sourceLine":"","asyncCause":null,"asyncCaller":null,"caller":null,"formattedStack":"ensureVsyncDisabled@chrome://mochikit/content/browser-test.js:588:19\n","nativeSavedFrame":{}}
[task 2023-03-01T20:55:35.873Z] 20:55:35     INFO - Stack trace:
[task 2023-03-01T20:55:35.873Z] 20:55:35     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:588
[task 2023-03-01T20:55:35.874Z] 20:55:35     INFO - GECKO(7484) | MEMORY STAT | vsize 2104241MB | vsizeMaxContiguous 66380809MB | residentFast 280MB | heapAllocated 96MB
[task 2023-03-01T20:55:35.874Z] 20:55:35     INFO - TEST-OK | dom/security/test/https-only/browser_httpsonly_speculative_connect.js | took 5357ms
[task 2023-03-01T20:55:35.874Z] 20:55:35     INFO - GECKO(7484) | [Child 4568: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 1990ce3fc00 == 1 [pid = 4568] [id = 5]
[task 2023-03-01T20:55:35.875Z] 20:55:35     INFO - GECKO(7484) | [Child 4568: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 3 (19907e7fc30) [pid = 4568] [serial = 14] [outer = 0]
[task 2023-03-01T20:55:35.875Z] 20:55:35     INFO - GECKO(7484) | [Child 4568: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 4 (1990ce40c00) [pid = 4568] [serial = 15] [outer = 19907e7fc30]
[task 2023-03-01T20:55:35.876Z] 20:55:35     INFO - checking window state
[task 2023-03-01T20:55:35.876Z] 20:55:35     INFO - TEST-START | dom/security/test/https-only/browser_redirect_tainting.js

Test and code haven't changed in a while. I think this is an issue in browser-test.js?

Component: DOM: Security → Mochitest
Product: Core → Testing
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.