-
Notifications
You must be signed in to change notification settings - Fork 2.5k
infra: fix flag recognition in bad build checks #13941
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
Conversation
@adisuissa fyi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this!
Tested Envoy: $ python3 infra/helper.py check_build envoy
...
INFO: performing bad build checks for /tmp/not-out/tmp8k2hlhbo/proxy_protocol_fuzz_test
INFO: performing bad build checks for /tmp/not-out/tmp8k2hlhbo/envoy_quic_h3_fuzz_test
INFO: performing bad build checks for /tmp/not-out/tmp8k2hlhbo/json_sanitizer_fuzz_test
INFO:__main__:Check build passed. |
/gcbrun trial_build.py all --fuzzing-engines libfuzzer --sanitizers address |
Hmm, the trial build fails with
which looks to be from 23c943f Will wait to check if the trial build fails in #13915 and if not then perhaps land that PR first. |
/gcbrun trial_build.py all --fuzzing-engines libfuzzer --sanitizers address |
Signed-off-by: David Korczynski <[email protected]>
97571d2
to
3b05627
Compare
/gcbrun trial_build.py all --fuzzing-engines libfuzzer --sanitizers address |
None of the failures are due to this PR. This is good to go. |
Some harnesses won't recognise the flags if
--
is not supplied, causing the bad build check to run the fuzzers forever or until they crash. This happens for Envoy.Tested this works on other projects as well, but will do a bit more testing before it's ready.