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.
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
fuzzing: minor change to build script #8223
Conversation
Signed-off-by: AdamKorcz <adam@adalogics.com>
|
Hi @AdamKorcz. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
The failing fuzzing CI run should be because OSS-Fuzz has still not pulled the recent upstream changes. |
|
@AdamKorcz Do you have a PR open for the upstream changes? |
It has already been merged: AdamKorcz/instrumentation@eca4ee9 |
|
Sorry. I was assuming there were some upstream changes we had to have in OSS-Fuzz.
Generally speaking, I'd like to merge changes when all tests are green. |
I think CIFuzz will go green when triggered tomorrow. |
|
Closing & reopening to trigger CI. I can't seem to trigger a rerun otherwise (maybe this has been sitting for too long?). |
|
@AdamKorcz Looks like this is still failing: |
|
This PR is stale because it has been open 90 days with no activity. This PR will be closed in 7 days unless new comments are made or the stale label is removed. |
|
This PR was closed because it has been stalled for 7 days with no activity. |
use flagged parameters to instrumentation utility.