| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 178893146
|
|
|
|
|
|
|
|
| |
Extend the protocol to support also showing meta data about
an action execution, if the underlying test action is able
to report it.
PiperOrigin-RevId: 177294531
|
|
|
|
|
|
|
|
| |
These are depended upon by analysis code, so need to live in the same library
as lib.analysis. Moving them here makes it possible to split the build-base
library into separate libraries for analysis, execution, and rules.
PiperOrigin-RevId: 164847161
|
|
|
|
|
|
|
|
| |
Also report test warnings, if any, for completed test actions in
the build event protocol.
RELNOTES: None
PiperOrigin-RevId: 161384061
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 159537816
|
|
|
|
|
|
|
|
| |
In multi-configuration builds, test can be run for different configurations as well. So
we have to report the configuration for each test as well.
Change-Id: I939cce7464823fbcd3c7161a50b41b94bbed8812
PiperOrigin-RevId: 155493397
|
|
|
|
|
|
|
|
|
|
|
| |
Change the BuildEvent interface to accept a generic class of converters.
In this way, we won't have to change it again in the future, once more
converters are needed. In fact, a new converter is needed right now (will
be added in a follow-up patch) to allow build events to know the name of
named artifact groups already reported in the stream.
Change-Id: Ibb32ea5fff361e21bcf2d34818d8351a1da7a2e3
PiperOrigin-RevId: 152131870
|
|
|
|
|
|
|
|
|
| |
Record the starting times of test actions, so that they can be reported
in the build event protocol.
Change-Id: I28e8d7d6ad39d91f4ffdd8a6161a5fc30f9a39b8
PiperOrigin-RevId: 151724760
|
|
|
|
|
|
|
|
| |
--
Change-Id: I07c15f7d232a3e9363ebedfb9b5523999630c401
Reviewed-on: https://cr.bazel.build/9450
PiperOrigin-RevId: 150887776
MOS_MIGRATED_REVID=150887776
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For a test result indicate if it was cached locally by the tool. Note
that this bit will not be set for tests cached by the remote execution.
Also clarify the meaning of the timing; it need not be set for locally
cached test results, but it may (and in this case reporting the timing
of the initial invocation of the cached test).
--
Change-Id: Ic83c4a58c1a85f6f4da82138999eaa545d8f60a6
Reviewed-on: https://cr.bazel.build/9376
PiperOrigin-RevId: 150442579
MOS_MIGRATED_REVID=150442579
|
|
|
|
|
|
|
|
|
|
| |
For tests, also provide information on the time the test took.
--
Change-Id: I8e71391e4dd97627d6293159a0cbb0d922683af7
Reviewed-on: https://cr.bazel.build/9214
PiperOrigin-RevId: 149547633
MOS_MIGRATED_REVID=149547633
|
|
|
|
|
|
|
|
|
|
|
| |
When a test is not run, because it was cached, we still expect the test to
be reported and to find a test log reported in the build-event protocol.
--
Change-Id: I806c757cdf8f46a5b687d29dec31ad4a289c4097
Reviewed-on: https://cr.bazel.build/8931
PiperOrigin-RevId: 147710591
MOS_MIGRATED_REVID=147710591
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For individual test actions, more useful data can be provided
than just the success status. Do so.
Also, to keep each log reported only once, send a new
TestAttempt event for the final test attempt, but don't
have the TestResult (which contains to union of all test
files) an instance of the BuildEvent.
As we now report test results in a separate object, drop
the test data and directly pass in the files created. In
this way, we also get all the moved files reported correctly
in the individual attempts.
--
Change-Id: Ic04b7bad4f92a381bd4d1b4ec91f743b89f81f84
Reviewed-on: https://cr.bazel.build/8694
PiperOrigin-RevId: 147149025
MOS_MIGRATED_REVID=147149025
|
|
For tests known to be flaky, additional attempts are run. Also report
about those in the build-event protocol.
--
Change-Id: I287b0b78478949abe5e14a9fafb1fd463aba8287
Reviewed-on: https://cr.bazel.build/8570
PiperOrigin-RevId: 146454273
MOS_MIGRATED_REVID=146454273
|