ci: add flaky-test management (#489)#1
Merged
Conversation
Switch the CI test steps to cargo-nextest (--retries 2) so a flaky test is retried and surfaced instead of silently failing the build. The coverage job uses the combined `cargo llvm-cov nextest` form so retries + the >=80% line-coverage gate both still run against the same collected data (the split nextest-run + llvm-cov form silently collects zero coverage, the bug in the first-pass PRs). Also drop the redundant full test/coverage re-run from the tag-driven publish workflow (#488): the merged tree already passed the ci.yml gate on its PR, so the tag-triggered job is build + package + publish only. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cargo test->cargo nextest run --all --retries 2(flaky tests retried + surfaced, not silently failing).cargo llvm-cov nextest --all --retries 2 --fail-under-lines 80form so retries and the >=80% line-coverage gate run against the same collected run (the split nextest-run + separate llvm-cov form collects zero coverage and fails the gate — the bug in the first-pass PRs, #488).publish.yml(tag-triggered): removed the redundantgatejob that re-ran fmt/clippy/full-test/coverage on every tag push. The merged tree already passed the ci.yml gate on its PR; the tag-triggered workflow is now build + package + publish only (#488 release-blocker).0.1.0->0.1.1(Cargo.toml+Cargo.lock), ci-only change, no behavior change to the crate.Stack: Rust (cargo workspace), CI-only change; no library code touched.
Test plan
publish.ymlstill builds/packages/publishes on tag push with no test re-runRefs #489, #488
Co-Authored-By: Claude noreply@anthropic.com