| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
This is in preparation for adding options to the class, which can be used
to modify the behavior of build events posted to the BEP.
PiperOrigin-RevId: 196997573
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Extend the build-event streamer to also report about stdout/stderr,
if provided. This information is reported in the progress events. At
the moment, we only report stdout/stderr in progress events we send
anyway, but the interface is generic enough that we could add time-based
reporting later, if needed. Also note, that at the end of the build, we
report the final progress event, so that all stdout/stderr generated before
the build-complete event get also reported in the build-event protocol.
Change-Id: If5dbd59c151edbce02d0a9b2e5938b63c0a5dc58
PiperOrigin-RevId: 154811110
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
Bazel-created files (like log files of test runs) are internally reported
as Paths. However, this is not always the most useful representation of the
location of that artifact for a consumer of build events. Therefore, support
a mapping of paths to more useful URIs.
--
PiperOrigin-RevId: 144843525
MOS_MIGRATED_REVID=144843525
|
| |
|
|
|
|
|
| |
Fixes #1863
--
MOS_MIGRATED_REVID=134767527
|
|
|
To organize a clean build event stream, certain infrastructural events
are necessary.
- If the build is aborted prematurely, certain expected events will not happen;
hence we have to close those leafs with an event indicating that the actual event
did not happen, as the build was aborted.
- Occasionally, we update on progress of the build, using special events; those are
also used to chain failure events that come before the build events for which they
are root cause are reported.
Add those.
--
Change-Id: Ibf86a313eb678822754b5e1f1e9d7f1a2cbeaaef
Reviewed-on: https://bazel-review.googlesource.com/#/c/6274
MOS_MIGRATED_REVID=134667915
|
ulfjack
Klaus Aehlig