Increase timeout threshold for fuzzer CI run #955
Merged
Conversation
This file contains 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
|
The original idea of reducing the fuzzer max size parameter didn't really work, so let's try increasing the timeout. OSS-Fuzz for comparison allows >= 1 hour before a timeout from what I see: https://github.com/search?q=repo%3Agoogle%2Foss-fuzz%20timeout&type=code |
isaacbrodsky
changed the title
ajfriend
approved these changes
Dec 23, 2024
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.
This is to avoid getting failures about the fuzzer timing out, which seems to happen since some cases may be slower than before. This is a bit inexact since perhaps there is some bad behavior with larger numbers of cells.
e.g. https://github.com/uber/h3/actions/runs/12289773577/job/34295819216?pr=953