| commit | 5d0e5a7ba415b981390bf9579da644e1065b2a36 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Thu Oct 06 14:39:42 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 06 14:41:00 2022 -0700 |
| tree | 622d041966832717de1705519af88f78932052bd | |
| parent | 40dc549ec449b61831a59cfacbcaa8dfa65343e6 [diff] |
Reinstate previous behavior of notifying the graph listener of `GET_BATCH` for every `DEP_REQUESTED` call. Recent optimizations in https://github.com/bazelbuild/bazel/commit/62d1b0b2b6c9646855698b5d7f9515521bc37a45 and https://github.com/bazelbuild/bazel/commit/243c2b78f634097d8f68d1317070e920cd4b891d mean that deps can now be requested via `get()` instead of `getBatch()`. It is possible that existing regression tests are no longer WAI because they are not getting the `GET_BATCH` event (i.e. they are passing but not testing what they intend to). Restoring the previous behavior is much easier than hunting down every test that is affected. PiperOrigin-RevId: 479416036 Change-Id: Iea3ac0a2ad02313dc8e61084fa5f585763a5967f
{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
