Repository navigation
Stabilize the remaining timed CI fuzz smoke checks - #49
Merged
Merged
Conversation
Signed-off-by: Vijay <evijay@gmail.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
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
Use fixed 10,000-input budgets and a two-minute overall timeout for the three
remaining timed PR/main CI fuzz smoke commands. Keep every target and assertion.
The scheduled security workflow's longer timed fuzzing is unchanged.
Main run 38191882262
failed on macOS in
FuzzTraceRecordwithcontext deadline exceededat the10-second duration boundary. The session tests, race tests and vet passed;
Ubuntu was cancelled by matrix fail-fast. This matches the timed-fuzz cancellation
failure described in Go #75804,
already referenced by the repository's security workflow.
Checks
Go 1.26.9, including the failing trace target.
This repair is separate from v0.8.0 preparation so release pins stay held for
approval. No release tags or publication.