Open Bug 1286893 Opened 9 years ago Updated 3 years ago

Web Platform Test timeout is accompanied by "JavaScript error: tests/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py, line 80: TypeError: window.win.timeout is not a function"

Categories

(Remote Protocol :: Marionette, defect, P3)

Version 3
defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: dholbert, Unassigned)

References

Details

The timeout in this web-platform-test run was accompanied by what looks like an (innocuous?) bug in Marionete: { TEST-START | /2dcontext/compositing/2d.composite.transparent.destination-in.html 02:26:07 INFO - PROCESS | 957 | MARIONETTE LOG: INFO: Timeout fired 02:26:07 INFO - PROCESS | 957 | JavaScript error: executormarionette.py, line 33: TypeError: window.wrappedJSObject.win.timeout is not a function 02:26:07 INFO - TEST-UNEXPECTED-TIMEOUT | /2dcontext/compositing/2d.composite.transparent.destination-in.html | expected OK } https://treeherder.mozilla.org/logviewer.html#?job_id=31780736&repo=mozilla-inbound Filing this bug on whatever's causing that "TypeError: window.wrappedJSObject.win.timeout is not a function"
I have tried to recreate this and can't so closing. If it reappears please reopen
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
This is appearing a lot. See for example https://treeherder.mozilla.org/#/jobs?repo=try&revision=33d9e29b239a1ac3b7ede7f86bf7b3654a4bc09e&selectedJob=190170896 https://taskcluster-artifacts.net/U_zo-7t_Q1iSC1z76GeAlw/0/public/logs/live_backing.log [task 2018-07-26T03:38:04.299Z] 03:38:04 INFO - TEST-START | /content-security-policy/generic/filesystem-urls-do-not-match-self.sub.html [task 2018-07-26T03:38:04.380Z] 03:38:04 INFO - PID 3193 | 1532576284375 Marionette DEBUG [2147483656] Frame script loaded [task 2018-07-26T03:38:04.380Z] 03:38:04 INFO - PID 3193 | 1532576284376 Marionette DEBUG [2147483656] Frame script registered [task 2018-07-26T03:38:04.683Z] 03:38:04 INFO - PID 3193 | 1532576284672 Marionette DEBUG [2147483659] Frame script loaded [task 2018-07-26T03:38:04.685Z] 03:38:04 INFO - PID 3193 | 1532576284673 Marionette DEBUG [2147483659] Frame script registered [task 2018-07-26T03:38:14.411Z] 03:38:14 INFO - PID 3193 | JavaScript error: tests/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py, line 80: TypeError: window.win.timeout is not a function [task 2018-07-26T03:38:19.431Z] 03:38:19 INFO - TEST-TIMEOUT | /content-security-policy/generic/filesystem-urls-do-not-match-self.sub.html | took 15129ms
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Web Platform Test timeout is accompanied by "JavaScript error: executormarionette.py, line 33: TypeError: window.wrappedJSObject.win.timeout is not a function" → Web Platform Test timeout is accompanied by "JavaScript error: tests/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py, line 80: TypeError: window.win.timeout is not a function"
This reproduces the bug locally for me: ./mach web-platform-tests --debugger=rr /fetch/api/abort/general.any.html Running under rr seems to slow things down enough to reproduce the JS error, but not enough to cause tests to fail.
I somewhat suspect this is because the content browser gets registered as a WebDriver window handle too soon, causing us to execute the test before it has been completely initialised. This would get fixed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=marionette-window-tracking.
Priority: -- → P3
Severity: normal → S3
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.