rules_python broken on CI Bazel@HEAD #1094
Comments
|
Auto-Sheriff identified this commit as the culprit: bazelbuild/bazel@0080572 |
|
/cc @comius |
|
Filed bazelbuild/rules_python#419 . |
bazel-io
pushed a commit
to bazelbuild/bazel
that referenced
this issue
Feb 19, 2021
Fixes a bunch of downstream breakages: bazelbuild/continuous-integration#1093 bazelbuild/continuous-integration#1094 bazel-contrib/rules_nodejs#2464 bazelbuild/rules_python#419 Turns out, the assertion that "Merkle tree computation uses `ActionInput.getExecPath()`" was only mostly correct: there was a place where the key of the input map was used instead. I'm somewhat surprised that this did not show up in our test battery, although, admittedly, "unsound directory as an input file in an external repository" doesn't sound like the most common use case. RELNOTES: None. PiperOrigin-RevId: 358366246
|
Confirming it is fixed https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1924 |
coeuvre
pushed a commit
to coeuvre/bazel
that referenced
this issue
Jul 15, 2021
… . Fixes a bunch of downstream breakages: bazelbuild/continuous-integration#1093 bazelbuild/continuous-integration#1094 bazel-contrib/rules_nodejs#2464 bazelbuild/rules_python#419 Turns out, the assertion that "Merkle tree computation uses `ActionInput.getExecPath()`" was only mostly correct: there was a place where the key of the input map was used instead. I'm somewhat surprised that this did not show up in our test battery, although, admittedly, "unsound directory as an input file in an external repository" doesn't sound like the most common use case. RELNOTES: None. PiperOrigin-RevId: 358366246
coeuvre
pushed a commit
to coeuvre/bazel
that referenced
this issue
Jul 15, 2021
… . Fixes a bunch of downstream breakages: bazelbuild/continuous-integration#1093 bazelbuild/continuous-integration#1094 bazel-contrib/rules_nodejs#2464 bazelbuild/rules_python#419 Turns out, the assertion that "Merkle tree computation uses `ActionInput.getExecPath()`" was only mostly correct: there was a place where the key of the input map was used instead. I'm somewhat surprised that this did not show up in our test battery, although, admittedly, "unsound directory as an input file in an external repository" doesn't sound like the most common use case. RELNOTES: None. PiperOrigin-RevId: 358366246
coeuvre
pushed a commit
to coeuvre/bazel
that referenced
this issue
Jul 16, 2021
… . Fixes a bunch of downstream breakages: bazelbuild/continuous-integration#1093 bazelbuild/continuous-integration#1094 bazel-contrib/rules_nodejs#2464 bazelbuild/rules_python#419 Turns out, the assertion that "Merkle tree computation uses `ActionInput.getExecPath()`" was only mostly correct: there was a place where the key of the input map was used instead. I'm somewhat surprised that this did not show up in our test battery, although, admittedly, "unsound directory as an input file in an external repository" doesn't sound like the most common use case. RELNOTES: None. PiperOrigin-RevId: 358366246
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1905#e9759395-101f-4047-b7c9-daa0fc4eb714
Broken only on Bazel@HEAD all OSes, verified it's not a one-off flake.
Failure has no culprit, looks like it might be machine configuration?
Not sure how to diagnose.
Error snippet:
(04:03:22) ERROR: /var/lib/buildkite-agent/builds/bk-docker-qfkh/bazel-downstream-projects/rules_python/experimental/examples/wheel/BUILD:169:9: Building wheel failed: Exec failed due to IOException: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/83072f5292f162d0736b24e3b6493e46/execroot/rules_python/rules_python/bazel-out/k8-fastbuild/bin/experimental/examples/wheel/someDir (No such file or directory)
The text was updated successfully, but these errors were encountered: