ci: use newer version of libFuzzer #4762
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
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.
Resolved issues:
Part of #4748
We are currently manually linking a specific version of libFuzzer that is 7 years old.
s2n-tls/codebuild/bin/install_libFuzzer.sh
Lines 33 to 35 in 7ba4a2f
Instead, we should use the newer version of libFuzzer that comes with clang.
Description of changes:
By using
-fsanitize=fuzzer, we automatically link the libFuzzer that comes with clang. This change removes the need to manually install or link the old library against our test executables. This will also make it easier to run fuzz tests locally since we no longer need to install libFuzzer.Testing:
Running FuzzBatch passed all test cases. Link to CodeBuild job
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.