Intermittent browser/extensions/webcompat/tests/browser/browser_shims.js | Test timed out - | Found a tab after previous test timed out: http://example.com/browser/browser/extensions/webcompat/tests/browser/shims_test.html
Categories
(Web Compatibility :: Tooling & Investigations, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: imoraru [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=377108769&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Ao1A4HSkS4KggR6X2HyrgQ/runs/0/artifacts/public/logs/live_backing.log
[task 2022-05-06T10:15:49.108Z] 10:15:49 INFO - TEST-PASS | browser/extensions/webcompat/tests/browser/browser_shims.js | Shim affected page correctly - true == true -
[task 2022-05-06T10:15:49.108Z] 10:15:49 INFO - Leaving test bound test_shim_disabled_overridden_by_pref
[task 2022-05-06T10:15:49.108Z] 10:15:49 INFO - Entering test bound test_shim
[task 2022-05-06T10:15:49.108Z] 10:15:49 INFO - Buffered messages finished
[task 2022-05-06T10:15:49.109Z] 10:15:49 INFO - TEST-UNEXPECTED-FAIL | browser/extensions/webcompat/tests/browser/browser_shims.js | Test timed out -
[task 2022-05-06T10:15:49.109Z] 10:15:49 INFO - GECKO(5025) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2022-05-06T10:15:49.110Z] 10:15:49 INFO - GECKO(5025) | MEMORY STAT heapAllocated not supported in this build configuration.
[task 2022-05-06T10:15:49.110Z] 10:15:49 INFO - GECKO(5025) | MEMORY STAT | vsize 130551231MB | residentFast 1068MB
[task 2022-05-06T10:15:49.111Z] 10:15:49 INFO - TEST-OK | browser/extensions/webcompat/tests/browser/browser_shims.js | took 120295ms
[task 2022-05-06T10:15:49.111Z] 10:15:49 INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-06T10:15:49.112Z] 10:15:49 INFO - TEST-UNEXPECTED-FAIL | browser/extensions/webcompat/tests/browser/browser_shims.js | Found a tab after previous test timed out: http://example.com/browser/browser/extensions/webcompat/tests/browser/shims_test.html -
[task 2022-05-06T10:15:49.279Z] 10:15:49 INFO - checking window state
[task 2022-05-06T10:15:50.446Z] 10:15:50 INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-06T10:15:50.446Z] 10:15:50 INFO - TEST-UNEXPECTED-FAIL | browser/extensions/webcompat/tests/browser/browser_shims.js | Uncaught exception received from previously timed out test - at chrome://mochitests/content/browser/browser/extensions/webcompat/tests/browser/head.js:46 - ReferenceError: ok is not defined
[task 2022-05-06T10:15:50.446Z] 10:15:50 INFO - Stack trace:
[task 2022-05-06T10:15:50.446Z] 10:15:50 INFO - testShimRuns@chrome://mochitests/content/browser/browser/extensions/webcompat/tests/browser/head.js:46:3
[task 2022-05-06T10:15:51.474Z] 10:15:51 INFO - GECKO(5025) | JavaScript error: chrome://mochikit/content/browser-test.js, line 1052: TypeError: can't access property "shift", currentScope.__tasks is null
[task 2022-05-06T10:15:51.478Z] 10:15:51 INFO - Console message: [JavaScript Error: "TypeError: can't access property "shift", currentScope.__tasks is null" {file: "chrome://mochikit/content/browser-test.js" line: 1052}]
[task 2022-05-06T10:15:51.555Z] 10:15:51 INFO - GECKO(5025) | Completed ShutdownLeaks collections in process 5127
[task 2022-05-06T10:15:51.573Z] 10:15:51 INFO - GECKO(5025) | Completed ShutdownLeaks collections in process 5182
[task 2022-05-06T10:15:51.642Z] 10:15:51 INFO - GECKO(5025) | Completed ShutdownLeaks collections in process 5183
[task 2022-05-06T10:15:51.833Z] 10:15:51 INFO - GECKO(5025) | Completed ShutdownLeaks collections in process 5099
[task 2022-05-06T10:15:53.286Z] 10:15:53 INFO - GECKO(5025) | Completed ShutdownLeaks collections in process 5025
[task 2022-05-06T10:15:53.287Z] 10:15:53 INFO - TEST-START | Shutdown
[task 2022-05-06T10:15:53.288Z] 10:15:53 INFO - Browser Chrome Test Summary
[task 2022-05-06T10:15:53.289Z] 10:15:53 INFO - Passed: 23
[task 2022-05-06T10:15:53.290Z] 10:15:53 INFO - Failed: 3
[task 2022-05-06T10:15:53.292Z] 10:15:53 INFO - Todo: 0
[task 2022-05-06T10:15:53.292Z] 10:15:53 INFO - Mode: e10s
[task 2022-05-06T10:15:53.293Z] 10:15:53 INFO - *** End BrowserChrome Test Results ***
Comment 1•4 years ago
|
||
Tom, can you take a look? It's only one failure and might have been just a fluke, but it's probably not a bad idea to look at it anyway. :)
Comment 2•4 years ago
•
|
||
This failure doesn't make much sense to me. Given the log, the ran just fine until the final test_shims test, and then the harness timed out waiting for shims_test.html to load, in this bit of code:
const tab = await BrowserTestUtils.openNewForegroundTab({
gBrowser,
opening: testPage, /* shims_test.html */
waitForLoad: true,
});
(Since if it got past that it would immediately show a line indicating a check to see if TP is attached to the tab, which should run just fine once that command completes, since it just checks the value of tab.ownerGlobal.gProtectionsHandler.blockers.TrackingProtection).
There is no real reason I can see for that page to not get to waitForLoad:true, since it's very straightforward:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf8">
<script>
window.shimPromise = new Promise(resolve => {
window.shimPromiseResolve = resolve;
});
window.optInPromise = new Promise(resolve => {
window.optInPromiseResolve = resolve;
});
</script>
<script onerror="window.shimPromiseResolve('error')" src="shims_test.js"></script>
</head>
<body>
<div id="shims"></div>
</body>
</html>
And shims_test.js is likewise straightforward and should not affect the waitForLoad condition:
if (window.doingOptIn) {
window.optInPromiseResolve(true);
} else {
window.shimPromiseResolve("did not shim");
}
So this seems like a weird random blip to me. I agree that we might as well wait and see whether this happens more often.
| Comment hidden (Intermittent Failures Robot) |
Comment 4•4 years ago
|
||
Alright, it's been failing once and only once, and from Tom's investigation, it doesn't look like it's a real issue, and probably was just a weird blip. Let's ignore this for now.
Description
•