fix(ci): nightly fuzz + bench workflows actually run#194
Merged
Conversation
Both nightly workflows have failed since introduction (2026-04-24) without ever succeeding — silently providing zero coverage. **fuzz-nightly**: cargo-fuzz defaults to musl target whose static libc is incompatible with AddressSanitizer; fails in <20s at the build phase. Add `--target x86_64-unknown-linux-gnu` (same fix as the PR-time fuzz smoke job in ci.yml from PR #142). **bench-nightly**: solver_worst_case/milp/worst_64 doesn't converge in any reasonable time on ubuntu-latest (single MILP solve takes tens of minutes). Gate behind `SPAR_BENCH_SLOW_MILP=1` env var so the nightly finishes; ad-hoc deep-bench runs can opt in. Plus `timeout-minutes: 60` ceiling as belt-and-braces. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
Both nightly workflows have failed since they were introduced on 2026-04-24 — silently providing zero coverage.
fuzz-nightly (#0a07f91): cargo-fuzz defaults to
x86_64-unknown-linux-musl. Static libc is incompatible with AddressSanitizer; the build aborts in <20s. Add--target x86_64-unknown-linux-gnu(same fix as the PR-time fuzz smoke job, PR #142).bench-nightly (#5268531):
solver_worst_case/milp/worst_64doesn't converge in reasonable time onubuntu-latest. Gate behindSPAR_BENCH_SLOW_MILP=1env var so the nightly job finishes; ad-hoc deep-bench runs can opt in. Addtimeout-minutes: 60ceiling.Test plan
cargo build -p spar-solver --benchesclean (verifies the env-gate compiles)🤖 Generated with Claude Code