| commit | 65210bada29254630670a0fee7cb6e5e01a4c3ca | [log] [tgz] |
|---|---|---|
| author | philwo <philwo@google.com> | Mon Jan 27 02:44:20 2020 -0800 |
| committer | Laurent Le Brun <laurentlb@gmail.com> | Thu Jan 30 17:53:32 2020 +0100 |
| tree | cdd53eddb07f9f6e215141d758fa2c13d5605e89 | |
| parent | 5f90ea9cb380eede9ee30cfb65a48bd78264b738 [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
