ci: bump fuzz job timeout to 45min#660
Open
dmtrKovalenko wants to merge 1 commit into
Open
Conversation
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
The
Fuzz Tests (windows-latest)job on #658 was killed by the job-leveltimeout-minutes: 20(https://github.com/dmtrKovalenko/fff/actions/runs/28889203324/job/85715598087).Root cause: the cache restore failed (cache service 400), so the seeded stress step alone took ~12min on a cold build, and the random step was cancelled mid-run before regressions even started. Even the passing ubuntu run finished at 19m8s — seconds under the limit. Three stress steps at ~6min each plus toolchain setup no longer fit in 20 minutes.
Bumps the fuzz job timeout to 45min, which still guards against a stuck watcher thread burning a full 6h CI slot while leaving headroom for cold-cache Windows builds.