You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This PR adds CIFuzz to Containerds CI. CIFuzz is a service offered by OSS-Fuzz and is recommended for all OSS-Fuzz projects. It will run all fuzzers for 10 minutes in the CI to catch low-hanging bugs and verify that no breaking changes to the fuzzing suite are introduced.
The time each fuzzer should run can be adjusted.
Only fuzzers that cover code that is affected by changes in PRs will run.
I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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/test-infra repository.
In addition to oss-fuzz's CIFuzz (see containerd#7052), this commit adds a small
shell script that run all fuzzing tests with go test -fuzz.
While running for 30 seconds would be too short to acutally find issues,
we want to make sure that these fuzzing tests are not fundamentally
broken.
Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
kzys
added a commit
to kzys/containerd
that referenced
this pull request
Jun 15, 2022
In addition to oss-fuzz's CIFuzz (see containerd#7052), this commit adds a small
shell script that run all fuzzing tests with go test -fuzz.
While running for 30 seconds would be too short to acutally find issues,
we want to make sure that these fuzzing tests are not fundamentally
broken.
Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
kzys
added a commit
to kzys/containerd
that referenced
this pull request
Jun 15, 2022
In addition to oss-fuzz's CIFuzz (see containerd#7052), this commit adds a small
shell script that run all fuzzing tests with go test -fuzz.
While running for 30 seconds would be too short to acutally find issues,
we want to make sure that these fuzzing tests are not fundamentally
broken.
Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
In addition to oss-fuzz's CIFuzz (see containerd#7052), this commit adds a small
shell script that run all fuzzing tests with go test -fuzz.
While running for 30 seconds would be too short to acutally find issues,
we want to make sure that these fuzzing tests are not fundamentally
broken.
Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
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.
This PR adds CIFuzz to Containerds CI. CIFuzz is a service offered by OSS-Fuzz and is recommended for all OSS-Fuzz projects. It will run all fuzzers for 10 minutes in the CI to catch low-hanging bugs and verify that no breaking changes to the fuzzing suite are introduced.
The time each fuzzer should run can be adjusted.
Only fuzzers that cover code that is affected by changes in PRs will run.
The CIFuzz documentation can be found here: https://google.github.io/oss-fuzz/getting-started/continuous-integration/