cts is not executed by ci workflow, cts_runner seems broken #6838
Labels
area: infrastructure
Testing, building, coordinating issues
type: enhancement
New feature or request
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: