Release: java_tools v13.4.0

[keertk]

Link to relevant issue and/or commit:
bazelbuild/bazel#20360
bazelbuild/bazel#20845 (comment)
bazelbuild/bazel#21119 (comment)

Other details: N/A

cc @bazelbuild/triage

[iancha1992]

@hvadehra could you please take a look at the failure?: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/243#018cea1b-42d3-48c0-acef-769990e20507

[fmeum]

@iancha1992 Could you post the error here? I can't access the link, but maybe I can help.

[iancha1992]

Here you go!:
java-tools-binaries-java_build_243_ubuntu.log

[fmeum]

Thanks, pretty sure this is bazelbuild/bazel#20753

[keertk]

Do we wait for bazelbuild/bazel#20753 or is there a workaround so we can proceed with the java_tools release in the meantime?

[fmeum]

@keertk You could try setting USE_BAZEL_VERSION to the latest release-7.0.1 commit for the CI job.

[keertk]

So this got rid of the failures from earlier but we're now seeing issues with bazel_java_test_local_java_tools_jdk11 -

• https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/246
• java-tools-binaries-java_build_246_ubuntu.log

Let me know if I'm missing something or if there's another step needed?

[fmeum]

@keertk the link isn't public, could you share the log?

[keertk]

@fmeum I've attached the log in the comment above as well.
Lmk if you'd like more details!

[fmeum]

I would have expected this line to have set zip_path to the copied zip, but apparently that doesn't happen. I don't know why.

Can you run the script with set -x to give us better logs?