| commit | 982a694b89c677dc63251b29e13caddc8582a506 | [log] [tgz] |
|---|---|---|
| author | Googler <leba@google.com> | Mon Mar 13 04:02:41 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 13 04:04:23 2023 -0700 |
| tree | ccc0c51a47a8e0fcc75d2d5dbc4dab2677aabddf | |
| parent | 9588ac74f2b51ef5f8789d2006d05e902813c930 [diff] |
[Skymeld] Don't propagate every event. Back in https://github.com/bazelbuild/bazel/commit/f7b8b7273bc65c655908081f41302a41a2cb3ff6, this filter was excluded from Skymeld mostly because of the filter's description. This was a mistake. Even without the boundary between analysis and execution in the traditional meaning, it still makes sense that events from an analysis node should not be propagated to its execution dependencies. This error resulted in an explosion in the number of SkyValues with Events attached to it. These events are then replayed in the subsequent incremental build. PiperOrigin-RevId: 516168703 Change-Id: I0a05a1f4a5beee84916ee0f0f41d79c3807304d0
{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
