bazel: Failed to create runfiles tree (build_bazel_rules_typescript)
Description of the problem:
Hi, I’m trying to setup bazel for my angular project: xLayers ( bazel branch ). I’m encountering this error after running a build command:
bazel build ...
Ouput:
Starting local Bazel server and connecting to it...
INFO: Analysed 36 targets (102 packages loaded).
INFO: Found 36 targets...
ERROR: /private/var/tmp/_bazel_wassim/a52e6be12b831a4a1e95901c31c1bbad/external/build_bazel_rules_typescript/internal/BUILD.bazel:31:1: Creating runfiles tree bazel-out/host/bin/external/build_bazel_rule
s_typescript/internal/tsc.runfiles [for host] failed: Process exited with status 1: Process exited with status 1
INFO: Elapsed time: 500.425s, Critical Path: 0.42s
INFO: 1 process: 1 darwin-sandbox.
FAILED: Build did NOT complete successfully
Bugs: what’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Clone this ( branch and just run a build command: bazel build ...
What operating system are you running Bazel on?
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G65
What’s the output of bazel info release
?
Build label: 0.16.1
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Aug 13 13:42:50 2018 (1534167770)
Build timestamp: 1534167770
Build timestamp as int: 1534167770
What’s the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?
git@github.com:xlayers/xlayers.git
0917e0b524d93ae6d33ba4fe18e7aa95dc15f9b2
39cbf2b43502ae7bf2e3b887429b855119c49cee
Have you found anything relevant by searching the web?
This. But it’s not solving this issue.
Any other information, logs, or outputs that you want to share?
My env:
- NVM: 8.11.3
- Node: 8.11.3
- NPM: 6.4.1
- TSC (local): 2.9.2
- Angular: 6.1.7
Bazel info:
Build label: 0.16.1
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Aug 13 13:42:50 2018 (1534167770)
Build timestamp: 1534167770
Build timestamp as int: 1534167770
Java info:
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
Issue openned in the bazelbuild/rules_typescript project as well.
cc @alexeagle
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22 (13 by maintainers)
Commits related to this issue
- Capture build-runfiles output. As https://github.com/bazelbuild/bazel/issues/6176 shows, it's very hard to debug runfiles building failures when all output is eaten. — committed to benjaminp/bazel by benjaminp 6 years ago
- Capture build-runfiles output. As https://github.com/bazelbuild/bazel/issues/6176 shows, it's very hard to debug runfiles building failures when all output is eaten. — committed to benjaminp/bazel by benjaminp 6 years ago
- Capture build-runfiles output. As https://github.com/bazelbuild/bazel/issues/6176 shows, it's very hard to debug runfiles building failures when all output is eaten. — committed to benjaminp/bazel by benjaminp 6 years ago
- Capture build-runfiles output. As https://github.com/bazelbuild/bazel/issues/6176 shows, it's very hard to debug runfiles building failures when all output is eaten. Closes #6305. PiperOrigin-RevId... — committed to bazelbuild/bazel by benjaminp 6 years ago
- Capture build-runfiles output. As https://github.com/bazelbuild/bazel/issues/6176 shows, it's very hard to debug runfiles building failures when all output is eaten. Closes #6305. P... — committed to luca-digrazia/DatasetCommitsDiffSearch by deleted user 2 years ago
@philwo after you resolve it would you mind sharing real quick how you debugged it. I’d love to share with others so we can help more in the future.
To be clear, the Bazel bug here is that the error reporting gave no output from the process that exited 1. I saw the same in Bazel 0.17
Can this considered to be fixed thanks to https://github.com/bazelbuild/bazel/commit/c63e4fedda25f5b4f547d9142138030ea8f278e1 ?
Found it:
which would have been seen if all runfiles building output wasn’t swallowed by Bazel. 😃
@dslomov - I also encountered this issue with the angular-bazel-example. My repro steps are here. I tried them again today with bazel 0.17.2 and I am still able to repro.
Make sure you checkout the exact commit I mentioned, otherwise it won’t fail. As @manekinekko said, the typescript issue must’ve been fixed.
got it, looking