WebGPU CTS upstream should only require generating WPT tests once
Categories
(Core :: Graphics: WebGPU, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: ErichDonGubler, Assigned: ErichDonGubler)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We vendor in new CTS test cases using dom/webgpu/tests/cts/vendor
. We currently have to work around gpuweb/cts
#1092 by stealing some files from npm run standalone
so that we can actually run the files generated by npm run wpt
(see also this SearchFox permalink).
This bug tracks the resolution of the upstream issue, and migration we want/need to do after it's fixed.
Assignee | ||
Comment 1•2 years ago
|
||
This change will need to piggyback or, at the very least, come after a CTS update.
Assignee | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:jimb, could you have a look please?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 3•2 years ago
|
||
Now that we're consuming upstream changes in CTS (namely,
gpuweb/cts
#1092), we need
not do this any more. Woot!
Depends on D181310
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
The review submission I've made here is ready to land (thanks for the review, :nical!), but only after we actually get CTS updated with bug 1834558. I believe the risk of the patch being invalidated is negligible, given the only purpose of this code is to update the CTS.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
Going to take this off my plate for now. I don't see this bug getting attended to any time soon, with the priorities the team currently has, but the patch here shouldn't change in the meantime.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
|
||
bugherder |
Description
•