| commit | 74c97f2a796c686ee39e3eaf66550bc266562059 | [log] [tgz] |
|---|---|---|
| author | leba <leba@google.com> | Tue Jan 25 02:09:45 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 25 02:11:49 2022 -0800 |
| tree | a44f090fc6da1c7c084294e542b2b13a30dd21a9 | |
| parent | 73a76a8af802f721f9de0f01026c50c4e72b2d35 [diff] |
Implement action conflict checking for --experimental_merged_skyframe_analysis_execution. We currently do action conflict checking between analysis & execution phases, with a full view of the action graph available. This becomes a challenge with interleaved analysis & execution phases since we don't have such view. This CL takes a new approach to resolving conflict: maintaining a stateful global action conflict checker that gets updated each time the analysis of a top-level target is completed. This state gets wiped before the build is over to release memory, and also to ensure incremental correctness. Notable Changes: 1. Addition of IncrementalArtifactConflictFinder, a stateful global action conflict checker. The checker uses a Trie to identify prefix conflicts. 2. BuildDriverFunction is now aware of artifact conflict checking. RELNOTES: None PiperOrigin-RevId: 424027061
{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:
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
