commit | bdf34d7fd9539411e93348ba25307f34362d9a42 | [log] [tgz] |
---|---|---|
author | philwo <philwo@google.com> | Mon Jan 27 02:44:20 2020 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 27 02:45:26 2020 -0800 |
tree | b953bd7aadadd9683e650ee8a5bed62a6dd4dbd4 | |
parent | 121933e38480922a509509116258242990fe9307 [diff] |
Fix race when extracting the install base when Bazel runs in a PID namespace. The PID is not a unique identifier in that case and if multiple instances of Bazel tried to extract itself to a shared location at the same time, they occasionally corrupted their temporary extraction directories. This is sometimes the case on CI systems (most notably Bazel's own CI), because a shared install base reduces the overhead of running the integration test suite a lot, as otherwise every test will extract its individual copy of Bazel. RELNOTES: None. PiperOrigin-RevId: 291685865
{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.
Follow our tutorials:
See CONTRIBUTING.md