Repository navigation
ci: run cli tests in their own job so runtime tests stop timing out - #6326
Conversation
Edit accuracy: accurate 271 (base branch 271), smooth 151 of thoseThe gate passes. Quarantined, measured but not gated (0) |
There was a problem hiding this comment.
Verdict: REQUEST CHANGES · 2 blocker · 0 important · 0 nits · head 562c323e
The shard split itself is right. Test now waits on test-cli and fails closed, and in this run Test (cli) took 5m15s and Test (runtime) 4m39s. There are two blockers, both inline: the required Format check is red, and the new job does not install the numpy that #6327 needs.
Scope
Read the full diff and grepped for other test-runtime / Test (runtime) consumers; Test is the only aggregator. Reproduced the oxfmt 0.41.0 output locally. git merge-tree of this head with #6327 d6ee1cfc merges cleanly, so git will not flag the numpy break.
The runtime test job ran cli, core and engine tests one after another and took 7 to 9.5 minutes against a 10 minute limit, so some PRs were cancelled right after their tests passed.
The cli tests now run in a parallel
Test (cli)job;Test (runtime)keeps core and engine. The requiredTestcheck waits on both and fails if either does not succeed. No required check names change.Before and after job times are in this PR's own CI run.