Skip to content
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

Pin Bazel to 4.2.2 #194

Merged
merged 1 commit into from
Jan 19, 2022
Merged

Conversation

fmeum
Copy link
Member

@fmeum fmeum commented Jan 19, 2022

Since OSS-Fuzz uses Bazelisk to invoke Bazel and rules_fuzzing does not
pin a Bazel version, the latest stable release of Bazel will be used.
This can (and did, twice now) unexpectedly break the build.

We should intead pin a Bazel version and consciously update it when we
add support for a new version.

Fixes #193

Since OSS-Fuzz uses Bazelisk to invoke Bazel and rules_fuzzing does not
pin a Bazel version, the latest stable release of Bazel will be used.
This can (and did, twice now) unexpectedly break the build.

We should intead pin a Bazel version and consciously update it when we
add support for a new version.
@fmeum
Copy link
Member Author

fmeum commented Jan 19, 2022

@stefanbucur This gets the pipeline green, but of course we should support the new Bazel version released just a few hours ago. I will work on that separately.

@fmeum fmeum marked this pull request as ready for review January 19, 2022 16:51
@stefanbucur stefanbucur merged commit d759d01 into bazel-contrib:master Jan 19, 2022
@fmeum fmeum deleted the fix-ci-fuzz-failure branch January 19, 2022 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clusterfuzz Jazzer builds fail in v0.3.0
2 participants