Summary
Stacked on #150 (base = fix/sweep-bugfixes-and-test-harness; retarget to main once that lands).
The test (3-OS matrix) and test-release jobs run cargo test --workspace --all-features, which also executes the feature-gated docker_e2e_* / setup_matrix_* suites. In these jobs they always soft-skip — no test images are built there, and macOS/Windows have no Docker — but each skip reports as a passing test. That inflates the green count by dozens per OS leg, and a regressed skip-guard could silently disable a real suite while CI stayed green.
Fix: build with --all-features --no-run (keeps compile-rot coverage for the gated suites), run with default features only. The gated suites keep executing for real in the dedicated e2e-docker and setup-matrix jobs.
Verification
- YAML validated.
- No test-selection change for default-feature suites; the only delta is that soft-skipping gated tests no longer appear in the run counts.
🤖 Generated with Claude Code
Note
Low Risk
Workflow-only test invocation change; default-feature test coverage is unchanged and gated suites still run in dedicated jobs.
Overview
The test (3-OS) and test-release jobs no longer run cargo test with --all-features. They now compile the full workspace with --all-features --no-run (still catching compile rot in feature-gated suites), then execute tests with default features only.
That stops docker_e2e_* / setup_matrix_* from running in those jobs and reporting dozens of soft-skip “ok” results where Docker/images are absent—so a broken skip guard can’t keep CI green. Real execution of those suites stays in e2e-docker and setup-matrix.
Both steps use bash with set -euo pipefail on the matrix test job.
Reviewed by Cursor Bugbot for commit b5513b4. Configure here.