Description of the problem / feature request:
When changing the output base. Bazel no longer recognizes the bazel-* symlinks as it's own and parses the contents resulting in build failues
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Example repo at https://github.com/adamporich/simple-bazel-test just consists of a single passing test.
> bazel --output_base=/tmp/bazel_1 test //...
INFO: Invocation ID: bda33659-6dbb-4d03-9f8f-fb273b5bafa9
INFO: Analyzed target //:test (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
Target //:test up-to-date:
bazel-bin/test
INFO: Elapsed time: 0.075s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
//:test (cached) PASSED in 0.0s
Executed 0 out of 1 test: 1 test passes.
INFO: Build completed successfully, 1 total action
> bazel --output_base=/tmp/bazel_2 test //...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: bb24dd33-6bbb-4c47-a943-ed4bfc65a34a
ERROR: error loading package 'bazel-bazel_symlink_test/external/bazel_tools/tools/cpp': in /home/gimo/dev/bazel_symlink_test/bazel-bazel_symlink_test/external/bazel_tools/tools/cpp/compiler_flag.bzl: Label '//tools/cpp:toolchain_utils.bzl' is invalid because 'tools/cpp' is not a package; perhaps you meant to put the colon here: '//:tools/cpp/toolchain_utils.bzl'?
INFO: Elapsed time: 1.998s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (8 packages loaded)
FAILED: Build did NOT complete successfully (8 packages loaded)
What operating system are you running Bazel on?
Above output is from Linux but occurs on Windows as well
What's the output of bazel info release?
> bazel info release
INFO: Invocation ID: 4d53a63f-daf5-43a2-b0ff-f3ab4927c52c
release 4.2.1
Have you found anything relevant by searching the web?
#11875 is a similar issue but in this case we don't need a root level glob to trigger
Any other information, logs, or outputs that you want to share?
I did try and use the https://docs.bazel.build/versions/4.2.1/command-line-reference.html#flag--experimental_convenience_symlinks option but it didn't seem to have an effect.
Description of the problem / feature request:
When changing the output base. Bazel no longer recognizes the
bazel-*symlinks as it's own and parses the contents resulting in build failuesBugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Example repo at https://github.com/adamporich/simple-bazel-test just consists of a single passing test.
What operating system are you running Bazel on?
Above output is from Linux but occurs on Windows as well
What's the output of
bazel info release?Have you found anything relevant by searching the web?
#11875 is a similar issue but in this case we don't need a root level glob to trigger
Any other information, logs, or outputs that you want to share?
I did try and use the https://docs.bazel.build/versions/4.2.1/command-line-reference.html#flag--experimental_convenience_symlinks option but it didn't seem to have an effect.