Remove redundant sandboxExecRoot creation in Darwin sandbox runner. Eliminate redundant upfront directory creation in `DarwinSandboxedSpawnRunner.prepareSpawn()` before sandbox filesystem setup so macOS sandbox reuse (`SandboxStash`) can move stashed sandbox directories into place without first creating and deleting an empty target directory on every spawn. Background: `DarwinSandboxedSpawnRunner.prepareSpawn()` previously created `sandboxExecRoot.getParentDirectory()` and `sandboxExecRoot` unconditionally before constructing `SymlinkedSandboxedSpawn` and calling `AbstractContainerizingSandboxedSpawn.createFileSystem()`. Because `AbstractContainerizingSandboxedSpawn.createFileSystem()` either moves a stashed sandbox directory into `sandboxExecRoot` on a `SandboxStash` hit (which had to delete the newly created empty `sandboxExecRoot` before `renameTo()`) or calls `sandboxExecRoot.createDirectoryAndParents()` on a stash miss, creating `sandboxExecRoot` upfront in `prepareSpawn()` caused unnecessary APFS metadata churn on every local spawn. RELNOTES: None. PiperOrigin-RevId: 1025778618 Change-Id: Iced9ad68c7a668cbd0321d8f18276a5d56320867
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md