Skip to content

ci: stop counting docker-e2e/setup-e2e soft-skips as passing tests - #151

Closed
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
fix/sweep-bugfixes-and-test-harnessfrom
ci/test-job-honesty
Closed

ci: stop counting docker-e2e/setup-e2e soft-skips as passing tests#151
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
fix/sweep-bugfixes-and-test-harnessfrom
ci/test-job-honesty

Conversation

@mikolalysenko

@mikolalysenko Mikola Lysenko (mikolalysenko) commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

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.

The test and test-release jobs ran `cargo test --workspace
--all-features`, which also RUNS the feature-gated docker-e2e and
setup-e2e suites. Those tests soft-skip as "ok" when no
socket-patch-test images exist — which is always true in these jobs (no
images are built there; macOS/Windows have no Docker at all). Every OS
leg therefore reported dozens of fake green tests, and a broken
skip-guard would disable a whole suite while CI stayed green.

Split build from run: --all-features --no-run keeps the compile-rot
coverage for the gated suites, the run step uses default features only.
The dedicated e2e-docker and setup-matrix jobs remain the places where
the gated suites actually execute.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mikolalysenko

Copy link
Copy Markdown
Collaborator Author

Folded into #150 — the stack was consolidated into a single PR at the author's request; this PR's commit is included there verbatim (cherry-picked, all tests green on the consolidated head).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant