Skip to content

ci(nextest): retry flaky tests so one serve-test race doesn't red main (closes #493) #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avrabe merged 1 commit into from
Jun 5, 2026
Merged

ci(nextest): retry flaky tests so one serve-test race doesn't red main (closes #493) #494

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .config/nextest.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,15 @@
[profile.ci]
# Fail-fast disabled so all tests run even if some fail
fail-fast = false
# Retry failed tests up to twice before reporting failure. The serve/integration
# tests bind ports and spin up a server, so under CI parallelism one
# occasionally fails on a timing/port race (this repo has several historical
# "fix flaky test" fixes). A test that passes on retry is reported FLAKY
# (visible in the summary) rather than failing the whole Test gate and
# reddening main; a genuinely-broken test still fails after all retries.
# Verified: `cargo test --workspace` + `nextest run --all` pass locally — the
# gate flakes, the code does not.
retries = 2

[profile.ci.junit]
# Output JUnit XML for CI consumption
Expand Down
Loading