| commit | ddc8a74b5916ac03e63de2cdd8a37ee5fffefdbc | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Wed Sep 11 06:14:09 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 11 06:15:54 2024 -0700 |
| tree | 0ea02a596420dcfb1fb0adab5003ac6cc5162ea4 | |
| parent | a7c2a4b91d4a7429bb9af2be79dfe63307bc9816 [diff] |
Include test outputs in TestResult. This makes it possible to retrieve them without doing I/O while emitting BEP events (*). I considered making the test outputs part of TestResultData (as suggested by the now deleted TODO in TestResult) but didn't like the resulting amount of proto conversion logic, and it's unclear that it fits with future plans. Also rename FailedAttemptResult to ProcessedAttemptResult, as after this CL it sometimes represents the result of the final, and possibly succeeding, test attempt. Progress on #17911. (*) It doesn't currently save much, because we need I/O anyway to compute digests for the BEP. However, it's incremental progress towards a better architecture (i.e. in the future we could pass artifacts and their metadata around, instead of just filenames). PiperOrigin-RevId: 673364262 Change-Id: I9266b7708d90ac252336c813a24c166712a699c7
{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
