Missing stderr for failed test XML creation #12649
Labels
area-EngProd
Bazel CI, infrastructure, bootstrapping, release, and distribution tooling
P3
We're not considering working on this, but happy to review a PR. (No assignee)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Milestone
Description of the problem / feature request:
I'm running some test of TensorFlow using bazel but on our multi-core POWER9 system it fails with e.g.
ERROR: /dev/shm/s3248973-EasyBuild/TensorFlow/2.4.0/fosscuda-2019b-Python-3.7.4/TensorFlow/tensorflow-r2.4/tensorflow/core/platform/BUILD:1142:11: failed (Exit 1): generate-xml.sh failed: error executing command
I.e. there is no good error message, it simply failed to execute that script which comes from the Bazel installation. I verified that the executed command (
bazel -s
) runs correctly and the script hence also existsThe problem is an unset LD_LIBRARY_PATH, see #12579, but the bug here is that stderr is not reported which made the trouble-shooting process incredibly laborious.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Sorry, only thing I have is the command I use to test TF:
What operating system are you running Bazel on?
RHEL 7.6
What's the output of
bazel info release
?release 3.4.1- (@non-git)
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.EXTRA_BAZEL_ARGS="--jobs=176 --host_javabase=@local_jdk//:jdk" ./compile.sh
Have you found anything relevant by searching the web?
#12579 #4137
Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: