-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fuzz: better configure checks for MSAN building #5422
Conversation
More compatible check for rust nightly Checks for CARGO_BUILD_TARGET Builds release or debug mode independently
Would it be useful to duplicate the ubuntu-18-04-fuzz CI test, use Rust nightly then do a post-configure check that this was setup correctly? |
For at least one with fuzzing, I think it would be useful to have Rust nightly, as it is needed to get the best out of fuzzing Rust. |
I'd probably go with a new Ubuntu 20.04 test. |
Ok, so... do you want this new ubuntu test qs part of this PR ? |
Doesn't really matter. But should probably be based on this PR. |
@jasonish do you manage to install/run dustup in Github CI builds ? |
Rustup is used in GitHub CI builds, see: https://github.com/OISF/suricata/blob/master/.github/workflows/builds.yml#L916 for an example. |
I see its download, but then I cannot use it as it is not in the PATH cf |
Merged in #5452, thanks! |
Link to redmine ticket:
None
Describe changes:
It seems #5411 was not good enough for oss-fuzz Docker
Replaces #5421 with version working bot locally and on oss-fuzz with catenacyber/oss-fuzz@4c922f1
Let's check if CI is happy with other systems