| commit | c2a6f0c38b75743158a3a8cbe7d6adf4202c2110 | [log] [tgz] |
|---|---|---|
| author | Googler <leba@google.com> | Wed May 24 06:18:40 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 24 06:19:59 2023 -0700 |
| tree | 02c8b86910e89dbb15b187dfd92bf5d6f71aa3d0 | |
| parent | 23f9c10b08f7637714906f6139e564b01bc74be7 [diff] |
Add `CoverageActionsFinishedId` to the `build_event_stream` proto. With Skymeld, the coverage actions are run _after_ the analysis & execution phase, since this is the earliest place where we can 1) have the list of analyzed tests and 2) request for a Skyframe evaluation. Unfortunately, this means that the info about the coverage artifacts would be missing in the BEP message triggered by the `TargetCompleteEvents`, which are sent at the end of the analysis & execution phase. This CL fixes that by adding an empty `CoverageActionsFinishedId`, which is listed as a `#postedAfter()` event of `TargetCompleteEvent`. This ensures that all info regarding the coverage artifacts is availble by the time we convert the `TargetCompleteEvent` to a BEP message. PiperOrigin-RevId: 534809359 Change-Id: Iabde183433a8492d9f009e7b235990efe7fc7069
{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
