Merged
Conversation
kaukabrizvi
approved these changes
Feb 17, 2026
dougch
approved these changes
Feb 17, 2026
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
3 participants
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.
Goal
Fix fuzz failure artifact upload paths in
runFuzzTest.shWhy
The scheduled fuzz test wasn't uploading failure artifacts from the correct path, resulting in the inability to reproduce observed fuzz test failures. The script runs with CWD=
tests/fuzz/but referenced./tests/fuzz/${TEST_NAME}_output.txt, resolving to a non-existent double-nested path.How
./tests/fuzz/${TEST_NAME}_output.txtto./${TEST_NAME}_output.txtcrash-*,timeout-*,leak-*,oom-*) which contain the exact inputs that triggered the failure and can be used to reproduce it locally${TEST_NAME}_results.txtwhich doesn't exist on the failure pathCallouts
Testing
Tested the failure upload path manually by temporarily disabling the negative test exception, invoking the scheduled fuzz job on CodeBuild, and confirming artifacts are uploaded to the corresponding S3 bucket.
Related
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.