ci(refactor): remove fuzz tests from Omnibus #4945
Merged
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.
Description of changes:
buildspec_fuzz_batch.yml
has coverage for all libcrypto that we have, while Omnibus is only doing fuzz tests with three libcrypto. Hence, we want to use thes2nFuzzBatch
job to replace the fuzz test part in Omnibus. This PR remove all fuzz tests from Omnibus.Call-outs:
openssl-1.0.2-fips
coverage in our fuzz test, and that is handled in ci: add openssl-1.0.2-fips to fuzz test #4942.Makefile
s. They are removed in chore: remove make fuzz and AFL fuzz #4808.Testing:
This will be tested by the CI. Also, the Lambda triggered test results will be attached to this section.
The results for the triggered Omnibus job, S2nIntegrationV2Batch2 job, Valgrind job, and s2nFuzzBatch job.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.