-
Notifications
You must be signed in to change notification settings - Fork 4.4k
"cannot relativize" crash #18321
Copy link
Copy link
Closed
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)team-Remote-ExecIssues and PRs for the Execution (Remote) teamIssues and PRs for the Execution (Remote) teamtype: bug
Description
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?
If bazel info release returns development version or (@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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)team-Remote-ExecIssues and PRs for the Execution (Remote) teamIssues and PRs for the Execution (Remote) teamtype: bug