You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: Skipping '//...': error loading package under directory '': error loading package '~/.cache/bazel-repo/bazel/_bazel_runner/d53d663888cb7d4fa0ce43a097f11d2b/install/rules_java/toolchains': at /__w/rules_ros2/rules_ros2/~/.cache/bazel-repo/bazel/_bazel_runner/d53d663888cb7d4fa0ce43a097f11d2b/install/rules_java/toolchains/java_toolchain_alias.bzl:17:6: Label '//java/common:java_common.bzl' is invalid because 'java/common' is not a package; perhaps you meant to put the colon here: '//:java/common/java_common.bzl'?
ERROR: error loading package under directory '': error loading package '~/.cache/bazel-repo/bazel/_bazel_runner/d53d663888cb7d4fa0ce43a097f11d2b/install/rules_java/toolchains': at /__w/rules_ros2/rules_ros2/~/.cache/bazel-repo/bazel/_bazel_runner/d53d663888cb7d4fa0ce43a097f11d2b/install/rules_java/toolchains/java_toolchain_alias.bzl:17:6: Label '//java/common:java_common.bzl' is invalid because 'java/common' is not a package; perhaps you meant to put the colon here: '//:java/common/java_common.bzl'?
Description of the bug:
Please see https://github.com/mvukov/rules_ros2/actions/runs/9665963740/job/26668343264?pr=331. Since 7.2.0 I get this error:
This is a PR in my repo where the failure happens: mvukov/rules_ros2#331. The CI config is in https://github.com/mvukov/rules_ros2/blob/main/.github/workflows/main.yml, and the build image in https://github.com/mvukov/bazel_builder/blob/ba61fac1727043eb4e80fdd895ad4ad158b7b141/Dockerfile.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Ubuntu 22.04
What is the output of
bazel info release
?7.2.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
The failures start with an update to Bazel 7.2.0, also happens with Bazel 7.2.1.
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: