fuzz_test: Reduce logging spam at allocation quotas, to avoid test timeouts
#6324
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
eddyashton
changed the title
fuzz_test: Reduce logging spam at allocation quotas, to avoid test timeouts
achamayou
approved these changes
Jul 3, 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.
fuzz_testis still extremely flaky following #6308, with some runs having a very low throughput (<200/s) and eventually timing out.Adding some logging to confirm the monkey-patch is present and has made a difference.
EDIT - After additional investigation, got local repro (requires SGX Debug Verbose), and found the spammy logs that are slowing things down.