-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Closed
Labels
team-Local-ExecIssues and PRs for the Execution (Local) teamIssues and PRs for the Execution (Local) teamtype: feature requestuntriaged
Description
Description of the feature request:
I often use --sandbox_debug to grab some paths from the output and inspect the execroot that an action failed with. I've noticed that with --incompatible_sandbox_hermetic_tmp=true (the default), that workflow doesn't work, so I have to flip it to false every time I want to do that. Should that be automatic with --sandbox_debug? Or should my workflow change since maybe we also don't want to keep both codepaths of incompatible_sandbox_hermetic_tmp around forever?
Which category does this issue belong to?
No response
What underlying problem are you trying to solve with this feature?
No response
Which operating system are you running Bazel on?
Linux
What is the output of bazel info release?
7.1.1
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 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
Metadata
Metadata
Assignees
Labels
team-Local-ExecIssues and PRs for the Execution (Local) teamIssues and PRs for the Execution (Local) teamtype: feature requestuntriaged