WebGPU: add test coverage for dedicated and shared workers via CTS
Categories
(Core :: Graphics: WebGPU, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox136 | --- | fixed |
People
(Reporter: ErichDonGubler, Assigned: ErichDonGubler)
References
(Blocks 1 open bug)
Details
Attachments
(5 files, 1 obsolete file)
Converts bug 1818042, comment 10 into a separate task.
Comment hidden (obsolete) |
Updated•1 year ago
|
Comment hidden (obsolete) |
Assignee | ||
Comment 3•1 year ago
•
|
||
Ran into some blockers here. I've spent a few days on this task, which culminated in discovering gpuweb/cts
#3834. IOW, contrary to appearances, there is not yet coverage for workers in upstream CTS that that's expected to work in a WPT environment. For this reason, no coverage for workers is available yet for the WPT target yet.
Un-assigning from myself, for now.
Comment 4•11 months ago
|
||
gpuweb/cts#3834 is marked as fixed. Do we have a bug filed for the CTS import that will bring that fix in?
Assignee | ||
Comment 5•11 months ago
•
|
||
:jimb: Yep! Patches for bug 1909753 that should bring it in...except, for some reason, re-vendored WPT output appears to produce both *.as_worker.js
and *.worker.js
tests 😣. Re-opened the upstream issue.
Assignee | ||
Comment 6•7 months ago
|
||
- Split components of
meta
-matching regex- Use named captures.
- Use
r
strings to eliminate backslash escaping. - Split into easier-to-read
concat!(…)
pieces.
- Use early return for regex capturing.
- Derive some stuff for
TimeoutLength
. - Factor out
WptEntry
construction ininsert_with_default_name
helper.
Updated•7 months ago
|
Assignee | ||
Comment 7•7 months ago
|
||
…that is, vendor test cases from cts-withsomeworkers.https.html
instead of cts.https.html
, which is a superset including worker
URL parameters.
TODO: I'm concerned about the sorting order of these tests. Maybe
worker
parameters should be reordered to be last?
Assignee | ||
Comment 8•7 months ago
|
||
Assignee | ||
Comment 9•7 months ago
|
||
My latest patch revisions and their first Try push (try:87ae36fb4afd
) gave way to some interesting discoveries today!
- Broadly speaking, CTS tests seem to Just Work™ and have similar test outcomes in service and dedicated worker contexts. Noice!
- Service workers seem to be universally failing to start WebGPU across the board. I'm going to start debugging at
gpuweb/cts
:bdee22a28e3bbd54c63ab8581fbdd82a12dc54fc
:src/common/runtime/helper/test_worker.ts
:162, where I suspect the URL for loading*.as_worker.js
URLs for the service worker needs to be fixed in our case. Hopefully this is easy to figure out, but if not, I honestly think that's a pretty punt-able piece of worker support.
The outlook for getting this test coverage in review before EOY is good. Exciting!
Assignee | ||
Updated•6 months ago
|
Comment 10•6 months ago
|
||
Comment 11•6 months ago
|
||
bugherder |
Assignee | ||
Comment 12•6 months ago
•
|
||
It turns out that service workers are blocked in CTS because they are written as ES modules. This is a terrific thing, except we don't support those in service workers, at least until bug 1360870 is resolved.
I'm going to move the scope of test coverage for service workers to bug 1938663. Will rename this bug accordingly.
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Comment 13•6 months ago
|
||
Assignee | ||
Updated•6 months ago
|
Comment 14•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Comment 15•6 months ago
|
||
Assignee | ||
Updated•6 months ago
|
Comment 16•6 months ago
|
||
bugherder |
Updated•6 months ago
|
Comment 17•6 months ago
|
||
Comment 18•6 months ago
|
||
bugherder |
Assignee | ||
Updated•6 months ago
|
Updated•5 months ago
|
Description
•