-
Notifications
You must be signed in to change notification settings - Fork 1.1k
cts is not executed by ci workflow, cts_runner seems broken #6838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
pr to repair cts_runner in #6840 but i will leave ci and workflow to maintainers |
We haven't really maintained the cts_runner of late, as we have two downstream projects running the cts (firefox and servo) - that said we'd definitely like this to keep working. |
It was added back shortly after, it was an administrative thing I'll see if I can tackle putting the cts job back |
It looks like there are some additional problems with the CTS after #7113. I had to update some deno crate versions, and I had to add a call to
|
Includes the following minor functional fixes to deno_webgpu: * Don't throw an error immediately when `create_buffer` is called with invalid usage flags. * Implement `on_submitted_work_done`. * Correct validation of GPUExtent3D element count. * Run without tracing (instead of panic) if the DENO_WEBGPU_TRACE env var is not set. Fixes gfx-rs#6838
Description
it seems like the cts workflow was removed, and thus this repository's ci has no way to use cts_runner since 34e947d
34e947d#diff-6867f1034f74cf18cb5e7345b15c2b5ae21eb47bb0a53d2b0c3bb4947753f4b6
cts_runner execution has since broken (rust panic aborts execution instead of simply failing), and before that, some cts pass/fail status regressed.
Expected vs observed behavior
cts_runner should not panic.
ci workflow should at least optionally execute deno cts. ideally, success of each individual test could be recorded periodically, or for each set of changes.
if cts_runner is executed and tracked by some other system, this should be documented and public. if cts_runner is no longer used, it should be removed.
Extra materials
cts_runner panics for everything in
test.lst
including unittests on 0f5f058 (tip of trunk)cts_runner passes two sets of tests on 5543961 (firefox dependency)
passing:
panic and abort:
exception and failure:
all seem to fail the same way
Platform
i'm running cts on macos sonoma and an m3 pro.
i understand macos was removed from CI test coverage some time ago, but all
cargo xtask test
(except stack depth) is still successful on 5543961 and tip of trunk.The text was updated successfully, but these errors were encountered: