I have confirmed bazel build //distro/... works locally as well as bazel test //java/test/..., but I was unable to get bazel test //test/... to work due to stardoc+/stardoc/proto/BUILD: no such target '@@stardoc+//stardoc/proto:stardoc_output_java_proto': target 'stardoc_output_java_proto' not declared in package 'stardoc/proto'

The CI failure is due to the missing mirror which I cannot add. If I was to remove this mirror url, then another test would fail due to Adoptium JDK sources being expected to have both a GitHub and a mirror url.

Missing mirror URLs:
  https://mirror.bazel.build/github.com/adoptium/temurin21-binaries/releases/download/jdk-21.0.4+7/OpenJDK21U-jdk_riscv64_linux_hotspot_21.0.4_7.tar.gz

You can file a mirror request under https://github.com/bazelbuild/bazel/issues/new/choose

You can file a mirror request under https://github.com/bazelbuild/bazel/issues/new/choose

Thank you. I've filed bazelbuild/bazel#24842.

With the mirror url now available, I have confirmed the failing test //test:check_remote_jdk_configs_test passes locally using Bazel 8.0.0. I am unable to retrigger the failing job in Buildkite, so a maintainer will need to help rerun CI again.

$ bazel test //test:check_remote_jdk_configs_test
INFO: Analyzed target //test:check_remote_jdk_configs_test (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
Target //test:check_remote_jdk_configs_test up-to-date:
  bazel-bin/test/check_remote_jdk_configs_test
INFO: Elapsed time: 160.602s, Critical Path: 160.48s
INFO: 2 processes: 1 action cache hit, 2 linux-sandbox.
INFO: Build completed successfully, 2 total actions
//test:check_remote_jdk_configs_test                                     PASSED in 160.4s

Executed 1 out of 1 test: 1 test passes.