Repository navigation
Give the fuzzing jobs a timeout they can finish inside - #36
Merged
Merged
Conversation
With the formatting gate fixed, Sustained Fuzzing ran for the first time in days and `parser-and-vm` was cancelled at exactly its 30 minute limit, part way through the sixth of seven fuzz steps. It was never going to finish: its own `max_total_time` budgets add up to 31 minutes before checkout, the nightly toolchain, `cargo install cargo-fuzz` and the build. `authority-and-durability` did pass, in 36 minutes against a 40 minute limit, so it had four minutes of headroom and a slow runner would have cancelled it too. Both now allow 45, which is their fuzz budget plus the three minutes of setup the successful job measured, plus margin. The budgets themselves are unchanged, so the work done per run is the same. Co-Authored-By: Claude Opus 5 (1M context) <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.
With the formatting gate fixed in #35, Sustained Fuzzing ran properly for the
first time in days.
parser-and-vmwas then cancelled at exactly its 30 minutelimit, part way through the sixth of its seven fuzz steps.
It was never going to finish. Its own
max_total_timebudgets add up to 31minutes, before checkout, the nightly toolchain,
cargo install cargo-fuzzandthe build. The job has been structurally impossible to complete for as long as
those budgets have been what they are.
authority-and-durabilitydid pass, in 36 minutes against a 40 minute limit.That is four minutes of headroom on a job whose fuzz budget is 33 minutes, so a
slow runner would have cancelled it too.
Both now allow 45 minutes: the fuzz budget plus the three minutes of setup the
successful job actually measured, plus margin. The fuzz budgets themselves are
unchanged, so each run does exactly the same amount of work as before.