Bazel 7.2.0 and 7.2.1: Label '//java/common:java_common.bzl' is invalid about bazel

[fmeum]

@hvadehra

[hvadehra]

I'm not familiar with github actions/cache but I suspect the issue lies there.

From the CI run logs, I see it starts with:

key: v3-bazel-repo-cache-gcc-8724efc64ec2ae6f9c8726587d03c992069750154b944bc682b0d378f7f9a03c
restore-keys: v3-bazel-repo-cache-gcc-

and at the end:

Cache restored successfully
Cache restored from key: v3-bazel-repo-cache-gcc-31b31c1d4e0c637ac53d7075d262ffafe4bac9f95f42e50866e71a607f2e9184

ISTM this might be an incorrect usage of restore-keys (I would have expected at the very least the bazel version as well to be included?)

[mvukov]

Hi, thanks for reaching out. I updated the key, but that didn't help unfortunately, please see https://github.com/mvukov/rules_ros2/actions/runs/9756344735/job/26926475145?pr=331.

For the reference, this was never a problem until Bazel 7.2.0.

[hvadehra]

Thanks for trying, it was just a shot in the dark :)

I presume this issue only occurs on CI, or have you managed to reproduce locally as well? If not, could you please let me know the simplest way to trigger CI so I can experiment?

[fmeum]

This line is problematic: https://github.com/mvukov/rules_ros2/blob/6b4ccf52bc43b1903467adb37f8bc71e30e602ea/.github/workflows/ci.bazelrc#L7

Bazel doesn't resolve ~ to the home directory and instead creates the cache in a subdirectory of the WORKSPACE called ~. It then descends into this "package" during the build, causing all kinds of weird issues.

Try passing in the path from the CI workflow's command line instead of via .bazelrc.

[mvukov]

@fmeum Thanks so much for the pointer. I also had to set XDG_CACHE_HOME as an absolute path. The PR builds now.