RUNFILES_MANIFEST_FILE is unset inside the sandbox #7994
Description
Description of the problem / feature request:
Bazel does not set RUNFILES_MANIFEST_FILE for tests when it should.
Update: only with sandboxing.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
BUILD:
sh_test(
name = "x",
srcs = ["x.sh"],
data = ["BUILD"],
)
x.sh:
#!/bin/bash
env | grep "^RUNFILES_.*="
When runfiles symlinks are enabled, all works fine: RUNFILES_DIR is defined, RUNFILES_MANIFEST_* isn't.
$ bazel test --enable_runfiles --build_runfile_manifests -t- --test_output=all //:x
...
==================== Test output for //:x:
RUNFILES_DIR=/usr/local/google/.../x.runfiles
================================================================================
When runfiles symlinks are disabled, RUNFILES_MANIFEST_FILE is missing:
$ bazel test --noenable_runfiles --build_runfile_manifests -t- --test_output=all //:x
...
==================== Test output for //:x:
RUNFILES_MANIFEST_ONLY=1
RUNFILES_DIR=/usr/local/google/.../x.runfiles
================================================================================
What operating system are you running Bazel on?
Debian
What's the output of bazel info release?
release 0.24.0