"I/O exception during sandboxed execution" when using tree artifacts #13229
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Local-Exec
Issues and PRs for the Execution (Local) team
type: bug
Description of the problem:
When generating an output artifact at a path that was previously a tree artifact, the incremental build fails with "I/O exception during sandboxed execution: Could not move output artifacts from sandboxed execution".
It seems that bazel makes the tree artifact directory read-only. A subsequent incremental build (where the tree artifact no longer exists, but a normal artifact would need to be created in that directory), can then fail with a permission error.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Repro script:
What operating system are you running Bazel on?
Ubuntu 18.04.3 LTS
What's the output of
bazel info release
?Also reproduces with bazelisk
USE_BAZEL_VERSION=last_green
(commit055c93d11ab20cc4479539b24bbdfa5cab78a342
).Have you found anything relevant by searching the web?
No.
Any other information, logs, or outputs that you want to share?
java.log shows a permission error:
The text was updated successfully, but these errors were encountered: