"cannot relativize" crash #18321
Assignees
Labels
P1
I'll work on this now. (Assignee required)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: bug
Comments
This was referenced May 4, 2023
sgowroji
added
the
team-Remote-Exec
coeuvre
added
P1
|
This is breaking many downstream projects: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3000 |
fweikert
pushed a commit
to fweikert/bazel
that referenced
this issue
May 25, 2023
Fixes bazelbuild#18321. PiperOrigin-RevId: 529656152 Change-Id: I06c60282893ef57dea837864031da0fe522937b8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
Started seeing this crash @ HEAD https://buildkite.com/bazel/apple-support-darwin/builds/1941#0187e83e-ff89-407c-930e-5575275ed97f https://buildkite.com/bazel/rules-swift-swift/builds/4211#0187e846-a4d0-43e1-9f8e-2bf03a0f2e87
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Seems like it doesn't repro locally. I imagine it requires a remote cache?
Which operating system are you running Bazel on?
macOS / Windows
What is the output of
bazel info release?8b60d6d
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: