| commit | d46aed621d1eebd166428bbf1e15ccd180e3c4b6 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Wed Mar 15 03:53:23 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Mar 15 03:54:45 2023 -0700 |
| tree | d5f488c9dd5ea85d2955d9ebe8d9b369d527f1e3 | |
| parent | 2fdf4eaa306811303abd1e6a03d6163db6f9aeb2 [diff] |
Fix state tracking for actions that run under multiple strategies. Each strategy can independently progress through the sequence of phases, but from a UI standpoint, we only care about (1) the set of strategies that have reported progress so far, and (2) the latest phase reported across all strategies. In addition, each action should contribute at most one unit to the action count, regardless of the number of strategies applied to it. This is not only simpler to track, but leads to more informative output in certain contexts. For example, if an action is simultaneously looked up in a remote cache and executed locally, we should not hide the fact that it was looked up once local execution starts (which could be an extremely short timespan). This is currently worked around by emitting the "running" event after the cache lookup is done [1], which is arguably incorrect since the action isn't running yet at that point. Related to #7345. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java;l=155;drc=32e4f23ec67909e92313be4d3334b62ccb490d55 PiperOrigin-RevId: 516782203 Change-Id: I710ac7199ec7a5fa5911788e3343445d5e57c85a
{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
