commit | a941db1a596acbd00d08974d881d80fc31aa6652 | [log] [tgz] |
---|---|---|
author | Googler <jhorvitz@google.com> | Thu Feb 29 12:53:39 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 29 12:54:45 2024 -0800 |
tree | 66e20b42462c53a82bc45dffd249ab7f04b423a9 | |
parent | ea88bb164ce2fb88ee12e828aa313e725687d669 [diff] |
Post the first 5 action rewind events instead of the top 5. A max of 5 action rewind events are posted as a sample, but we currently store every action rewind event in the whole build, then when the build ends, we sort them by number of lost inputs and take the top 5. In order to limit memory use when there is a lot of rewinding, just take the first 5 such events and do away with sorting by number of lost inputs. Note that we still post the total number of lost inputs in the build. Removed assertions in a couple tests about exactly which events are posted since it can now be nondeterministic. I think these tests still offer excellent coverage. PiperOrigin-RevId: 611566530 Change-Id: I190e6fc53d17945848fb2cfa7ae9bf6052450921
{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