Skip to content

Fix leading slash exit in fuzz test #1813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Sep 17, 2024
Merged

Fix leading slash exit in fuzz test #1813

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
c80be19
Fix leading slash exit in fuzz test
prestonvasquez Sep 16, 2024
c3a08f2
Merge branch 'master' into fix-leading-slash-fuzz-exit
prestonvasquez Sep 16, 2024
fd8cdbd
Change directory before tarring
prestonvasquez Sep 17, 2024
06c1cc8
Merge branch 'fix-leading-slash-fuzz-exit' of github.com:prestonvasqu…
prestonvasquez Sep 17, 2024
6065a42
Merge branch 'master' into fix-leading-slash-fuzz-exit
prestonvasquez Sep 17, 2024
36d6cb5
Fix indentation
prestonvasquez Sep 17, 2024
b7c4223
Update .evergreen/run-fuzz.sh
prestonvasquez Sep 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .evergreen/run-fuzz.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ done
# If the fuzz directory exists, then tar it up in preparation to upload to S3.
if [ -d $PROJECT_DIRECTORY/fuzz ]; then
echo "Tarring up fuzz directory"
tar -czf $PROJECT_DIRECTORY/fuzz.tgz $PROJECT_DIRECTORY/fuzz
tar -czf $PROJECT_DIRECTORY/fuzz.tgz --absolute-names $PROJECT_DIRECTORY/fuzz
Copy link
Member Author

@prestonvasquez prestonvasquez Sep 16, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note the fuzz test still fails in CI, but because of a legitimate issue. See GODRIVER-3346 for more information.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the proper way is to instead cd $PROJECT_DIRECTORY and then run tar -cfz fuzz.tgz ./fuzz


# Exit with code 1 to indicate that errors occurred in fuzz tests, resulting in corpus files being generated.
# This will trigger a notification to be sent to the Go Driver team.
Expand Down
Loading