Enable incremental upgrading of test tier for WebGPU CTS
Categories
(Core :: Graphics: WebGPU, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: ErichDonGubler, Assigned: ErichDonGubler)
References
(Blocks 1 open bug)
Details
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Assignee | ||
Comment 1•8 months ago
|
||
I currently plan on doing this via the implementation-status
, a la web-platform-test
jobs that use implementation-status
already in Firefox CI. CC'ing :jmaher, who I'll likely be contacting soon with questions. 🙂
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•7 months ago
|
Assignee | ||
Updated•7 months ago
|
Comment hidden (obsolete) |
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Comment hidden (obsolete) |
Assignee | ||
Comment 4•6 months ago
•
|
||
After discussing the implementation-status
WPT property with :jgraham, it turns out that the only valid values relevant to use are implementing
and backlog
(before, I thought a default
value was in the set of valid values due to a docs. issue). We might want to use a tag
value to differentiate more than 2 stages later, but I think we need to focus on having 2 stages right now if that's easily achievable with implementation-status
. Will move forward with implementing
and backlog
for now.
Assignee | ||
Comment 5•5 months ago
|
||
Assignee | ||
Comment 6•5 months ago
|
||
Assignee | ||
Comment 7•5 months ago
|
||
Updated•5 months ago
|
Updated•5 months ago
|
Assignee | ||
Comment 8•5 months ago
|
||
We need to do this because of 0.25 timeout multiplier imposed on
--backlog
WPT tests; permalink:
https://searchfox.org/mozilla-central/rev/eb4700a6be8371fe07053bc066c2d48ba813ce3d/testing/mozharness/scripts/web_platform_tests.py#433-435
Updated using:
moz-webgpu-cts update-expected --preset new-fx …
with reports from
try:4ee59d698a3a,
version 0.9.0, then…- …not committing new metadata files in
testing/web-platform/mozilla/meta/webgpu/webgpu/
, which will be
handled in a subsequent patch from this stack. - …some manual effort to remove
if os == "mac": SKIP
outcomes for
various jobs in MacOS'webgpu-backlog6
tasks. Will follow up with
these in bug
1893047.
Assignee | ||
Comment 9•5 months ago
|
||
Assignee | ||
Comment 10•5 months ago
|
||
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Comment 11•5 months ago
|
||
Pushed by egubler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ea0e5c68965a test(webgpu): skip `not-implementing` tests in CTS r=webgpu-reviewers,teoxoy https://hg.mozilla.org/integration/autoland/rev/451636e3ac1e test(wpt): pass test paths via `--include-file` on Windows r=webgpu-reviewers,teoxoy https://hg.mozilla.org/integration/autoland/rev/d5bd60ebaf65 test(webgpu): split (most) tests from `webgpu` into `webgpu-backlog` r=webgpu-reviewers,taskgraph-reviewers,bhearsum,nical
Comment 12•5 months ago
|
||
bugherder |
Assignee | ||
Updated•5 months ago
|
Comment 13•5 months ago
|
||
Pushed by egubler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6796f3c9a6da test(webgpu): update outcomes for backlog timeout multiplier r=webgpu-reviewers,teoxoy https://hg.mozilla.org/integration/autoland/rev/f207a8a61d87 test(webgpu): mark `webworker` CTS cases as `expected: SKIP` r=webgpu-reviewers,teoxoy https://hg.mozilla.org/integration/autoland/rev/9382506b792f test(webgpu): remove unused `fs::existing_file` in CTS vendoring script r=webgpu-reviewers,teoxoy
Comment 14•5 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6796f3c9a6da
https://hg.mozilla.org/mozilla-central/rev/f207a8a61d87
https://hg.mozilla.org/mozilla-central/rev/9382506b792f
Description
•