| commit | df1e1f64a542c9789d7f981b83efff96d9a07fe0 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Wed Dec 13 11:17:35 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 13 11:19:14 2023 -0800 |
| tree | 0e208620a21add11b953bed9a57c0b9f421293a7 | |
| parent | b13fd921b575172ebc6562798c204fd86fe5282e [diff] |
Clean up the interface of `EvaluationProgressReceiver#evaluated`. Combine the two parameters `EvaluationState` and `EvaluationSuccessState` (each essentially booleans) into a single `EvaluationState` object with two boolean methods. Improve documentation and verbiage about what these mean - the previous `BUILT`/`CLEAN` distinction was confusing because `CLEAN` included both the case where a node was already up to date and the case where it was computed and evaluated to the same value. Progress receivers just want to know whether the node changed, so directly provide this information. Also, I'm now using the term "built" to mean that `SkyFunction#compute` was invoked. Also, remove the unnecessary lazy `Supplier` wrapper for the success state. PiperOrigin-RevId: 590659574 Change-Id: If76829d1336098c55d8eee29358cabd8da31a95e
{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
