3 web-locks/ tests are expected TIMEOUT
Categories
(Testing :: web-platform-tests, defect)
Tracking
(firefox79 fixed)
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed |
People
(Reporter: jmaher, Assigned: jgraham)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
I find that these tests in web-locks/ are expected timeout:
/web-locks/frames.tentative.https.html
/web-locks/query-ordering.tentative.https.html
/web-locks/workers.tentative.https.html
I have verified these timeout locally on my windows 10 instance.
here is the error I see in the console:
/web-locks/frames.tentative.https.html:
JavaScript error: https://web-platform.test:8443/web-locks/resources/iframe.html, line 18: TypeError: can't access property "request", navigator.locks is undefined
/web-locks/query-ordering.tentative.https.html:
JavaScript error: https://web-platform.test:8443/web-locks/resources/iframe.html, line 43: TypeError: can't access property "request", navigator.locks is undefined
/web-locks/workers.tentative.https.html:
TypeError: can't access property "request", navigator.locks is undefined
https://web-platform.test:8443/web-locks/resources/worker.js:15:0
these are also missing the proper bugzilla component.
:jgraham, can you help find a triage owner for these tests so we can start looking into if we support web-locks/*tentative.https.html tests or how we can fix the tests.
|
Assignee | |
Comment 1•4 years ago
|
||
This avoids needless timeouts
|
||
Updated•4 years ago
|
|
|
Assignee | |
Comment 2•4 years ago
|
||
Added a patch that will stop the timeouts. https://github.com/mozilla/standards-positions/issues/64 seems to be the standards-position for this; :asuth might know if we're planning to work on it in the foreseeable future.
|
|
||
Updated•4 years ago
|
|
||
Comment 3•4 years ago
|
||
It's on the short-list for implementation, but 2020 H2 OKR scheduling is still to happen in the future.
|
||
Comment 8•4 years ago
|
||
| bugherder | ||
Description
•