ci(libscap): Run libscap fuzzer in CI - #3063
Conversation
Generate a targeted synthetic corpus and run the fuzzer in a bounded CI job. Signed-off-by: tks98 <travis.kenneth.smith@gmail.com>
|
@tks98: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tks98 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Perf diff from master - unit testsHeap diff from master - unit testsHeap diff from master - scap fileBenchmarks diff from master |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3063 +/- ##
=======================================
Coverage 75.94% 75.94%
=======================================
Files 300 300
Lines 33276 33276
Branches 5057 5055 -2
=======================================
Hits 25271 25271
Misses 8005 8005
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
What type of PR is this?
/kind test
Any specific area of the project related to this PR?
/area libscap
/area tests
Does this PR require a change in the driver versions?
No.
What this PR does / why we need it:
This follows up on #2857 by running the libscap fuzzer using the synthetic corpus only for 15 seconds for simplicity.
The idea would be that a long running fuzz job would be added to oss-fuzz and this would just validate functionality and severe regressions.
I was able to test this CI stage using act locally to try to validate it works as close as I could to actual GitHub actions but can make any changes required once it's actually run here.
Does this PR introduce a user-facing change?: