| commit | 658ba15d9f37969edfaae507d267ee3aaba8b44e | [log] [tgz] |
|---|---|---|
| author | Googler <yuyueny@google.com> | Fri Dec 16 13:30:29 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Dec 16 13:31:53 2022 -0800 |
| tree | b096ad602b90cf62f09206ce99bc879a1603808f | |
| parent | 93f5db5d8860c95ec2ad00ed33dfd5b9bb0013af [diff] |
Add drop state nodes flag and apply it to `SkyframeProgressReceiver#evaluated()` method. Due to the fact that the vast majority of the `_STATE` nodes only have one rdeps, we decided to drop them after the evaluation of `FILE` or `DIRECTORY_LISTING` nodes. So in this change: * A new `--experimental_drop_state_nodes` is added in `CommonCommandOptions` in order to control whether `_STATE` nodes should be dropped or not; * Inject the flag to `SequencedSkyframeExecutor` and `SkybuildV2SkyframeExecutor`; * `SkyframeProgressReceiver#evaluated(...)` method decides whether to drop `_STATE` nodes based on the flag value and the type of input `SkyKey`. PiperOrigin-RevId: 495949249 Change-Id: I7b4b84f7d91e8c3a7ce44f5ccb1af62ed134ebeb
{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
