Status of Bazel 5.0.0-pre.20210510.2

[fweikert]

• Expected release date: Last week of May / First week of June

Task list:

• Pick release baseline: 8a42645 with cherrypicks e3c78c4 1f52e9a
• Create release: https://releases.bazel.build/5.0.0/rolling/5.0.0-pre.20210510.2rc1
• Check downstream projects: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2052
• Push the release:
• Update the release page

[fweikert]

RBE is red: https://buildkite.com/bazel/bazel-bazel/builds/16384

[davido]

@fweikert

red build is good. Much worse is the situation with green build that produces broken result.

As explained in #7849 (comment) Bazel issues this warning:

WARNING: Option 'java_toolchain' is deprecated

and ignores java_toolchain, for example for projects that want to produce Java 11 major byte code.

Unfortunately, the attempt to un-flip --incompatible_use_toolchain_resolution_for_java_rules=false doesn't work.

The only way forward is to migrate to incompatible_use_toolchain_resolution_for_java_rules. Something like: [1] is needed for all projects that use custom java_toolchain.

Can this be clarified in the release notes, or alternatively avoid releasing Bazel in this state?

[1] https://gerrit-review.googlesource.com/c/gerrit/+/291864

[haberman]

My builds have just started failing (since yesterday). I am using use_bazel.sh latest.

+ use_bazel.sh latest
+ filename=bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ cmd='curl  -sLO --retry 5 --retry-max-time 10   https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh'
+ eval 'curl  -sLO --retry 5 --retry-max-time 10   https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh'
++ curl -sLO --retry 5 --retry-max-time 10 https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ sudo mkdir -p /usr/local/bazel/5.0.0-pre.20210510.2.2
+ chmod 755 bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ command='sudo "./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh" "--prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2" '
+ eval 'sudo "./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh" "--prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2" '
++ sudo ./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh --prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2
./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh: 1: ./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh: Syntax error: redirection unexpected

https://source.cloud.google.com/results/invocations/1d3fd36e-7834-46c8-a4fb-17faff0bc25b/targets/upb%2Fubuntu%2Fpresubmit/log

It looks like the Linux installer for 5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh is broken somehow?

[haberman]

Any comment on the error above? This is breaking all of my Kokoro builds on https://github.com/protocolbuffers/upb at the moment.

[matthewstevenson88]

+1, also breaking my Kokoro builds.

[hlopko]

Could we re-check downstream projects? Rules Rust have been reenabled recently (and there's a lot of red stuff in the link, is that expected and ok?)

[matthewstevenson88]

I'm still seeing failures as this morning. The relevant logs are here:

+ use_bazel.sh latest
+ filename=bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ cmd='curl  -sLO --retry 5 --retry-max-time 10   https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh'
+ eval 'curl  -sLO --retry 5 --retry-max-time 10   https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh'
++ curl -sLO --retry 5 --retry-max-time 10 https://storage.googleapis.com/bazel/5.0.0-pre.20210510.2.2/release/bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ sudo mkdir -p /usr/local/bazel/5.0.0-pre.20210510.2.2
+ chmod 755 bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh
+ command='sudo "./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh" "--prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2" '
+ eval 'sudo "./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh" "--prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2" '
++ sudo ./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh --prefix=/usr/local/bazel/5.0.0-pre.20210510.2.2
./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh: 1: ./bazel-5.0.0-pre.20210510.2.2-installer-linux-x86_64.sh: Syntax error: redirection unexpected

This looks similar to the logs in @haberman's PR here: protocolbuffers/upb#400

[fweikert]

Back from OOO. Several thoughts:

1. This very first rolling release was mostly a test for our release infrastructure. I didn't expect any real usage yet, but in hindsight I should have communicated that clearly.
2. We (Bazel team) still need to determine and document our SLO for such releases. For example, which tests have to be passed in order to proceed with a release.
3. Since rolling releases are tied to Blaze releases we'll likely have weekly releases in the future, which means that we probably won't cherrypick commits (still being debated).
4. Re Kokoro: Can you use the latest LTS release instead? https://api.github.com/repos/bazelbuild/bazel/releases/latest ignores rolling releases since they're marked as "prerelease".

[fweikert]

The most recent rolling release is https://github.com/bazelbuild/bazel/releases/tag/5.0.0-pre.20210520.7, and there will be another one tomorrow if today's Blaze release doesn't get rolled back.

[matthewstevenson88]

Thanks @fweikert, downgraded our Bazel version for now.