Skip to content

Commit c0a3c55

Browse files
claudeBrooooooklyn
authored andcommitted
fix: exclude custom-harness packages from nextest, run them with cargo test
cargo-nextest can't discover tests in packages with `harness = false` (e2e_snapshots, plan_snapshots) because they output custom formats instead of the standard libtest listing. Split the musl test run: - nextest for standard-harness tests (parallel, per-process isolation) - cargo test for custom-harness packages (already run sequentially) https://claude.ai/code/session_011H8UR3gS6hoyQAf2x7Dfw8
1 parent 379b3d9 commit c0a3c55

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

.github/workflows/ci.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,8 +175,11 @@ jobs:
175175
# Use cargo-nextest: it runs each test in its own process, avoiding
176176
# musl's fork()-in-multithreaded-process SIGSEGV while keeping parallel
177177
# execution (across processes instead of threads within one process).
178+
# Exclude packages with custom test harnesses (harness = false) since
179+
# nextest can't discover their tests; run those with cargo test instead.
178180
- run: cargo install cargo-nextest --locked
179-
- run: cargo nextest run
181+
- run: cargo nextest run --workspace --exclude vite_task_bin --exclude vite_task_plan
182+
- run: cargo test -p vite_task_bin -p vite_task_plan
180183

181184
fmt:
182185
name: Format and Check Deps

0 commit comments

Comments
 (0)