-
Notifications
You must be signed in to change notification settings - Fork 377
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
Bazel not building #2690
Labels
Comments
mhutchinson
added a commit
to mhutchinson/trillian
that referenced
this issue
Apr 4, 2022
mhutchinson
added a commit
that referenced
this issue
Apr 5, 2022
mhutchinson
added a commit
to mhutchinson/trillian
that referenced
this issue
May 26, 2022
To our knowledge nobody was using this and python support was already removed in google#1964. If the removal of this affects anybody and they let us know, then I'm open to bringing this back. Without knowing it's used, this is something that breaks from time to time and demands investigation to keep CI working and thus hard to justify the return on investment. Fixes google#2690
mhutchinson
added a commit
that referenced
this issue
May 26, 2022
To our knowledge nobody was using this and python support was already removed in #1964. If the removal of this affects anybody and they let us know, then I'm open to bringing this back. Without knowing it's used, this is something that breaks from time to time and demands investigation to keep CI working and thus hard to justify the return on investment. Fixes #2690
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zlib 1.2.12 was released on March 27 2022, and it looks like they've immediately taken down the 1.2.11 release for download. The HEAD version of protobuf is still pinned against the old version: https://github.com/protocolbuffers/protobuf/blob/main/protobuf_deps.bzl#L35
For now, recommend removing bazel from cloudbuild integration. Leave this open to determine if we go all the way and remove it, or try to repair (or at least, await upstream repair).
The text was updated successfully, but these errors were encountered: