| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Fix sandboxing when spawn outputs differ from action outputs. |  Benjamin Peterson | 2017-07-19 |
| | | | | | | | | | | | | | TestRunner actions are special because their action outputs are different from their spawn outputs. If there's a spawn output that's not an action output, SymlinkExecroot can't rely on the parent directories for that output existing in the real execroot. Thus, copyOutputs() must ensure the real execroot has the relevant ancestral directories before copying the output over. Change-Id: I84fd69cd51628c51de9c8993b6a4407bbff038a0 PiperOrigin-RevId: 162470058 | ||
| * | Rewrite all the sandbox strategy implementations |  ulfjack | 2017-07-12 |
| - Make use of existing abstractions like SpawnRunner and SpawnExecutionPolicy. - Instead of having the *Strategy create a *Runner, and then call back into SandboxStrategy, create a single SandboxContainer which contains the full command line, environment, and everything needed to create and delete the sandbox directory. - Do all the work in SandboxStrategy, including creation and deletion of the sandbox directory. - Use SpawnResult instead of throwing, catching, and rethrowing. - Simplify the control flow a bit. PiperOrigin-RevId: 161644979 | |||
 |
index : bazel | |
| a fast, scalable, multi-language and extensible build system |
| aboutsummaryrefslogtreecommitdiffhomepage |