diff options
author | buchgr <buchgr@google.com> | 2017-05-30 12:18:20 +0200 |
---|---|---|
committer | László Csomor <laszlocsomor@google.com> | 2017-05-30 12:51:48 +0200 |
commit | 229f393bf460700594ae032a551879e026bd0b91 (patch) | |
tree | 63c5ad69d22f63321b6cce4cee63042a0c35f316 /src/test/java/com/google/devtools/build/lib/syntax/FunctionTest.java | |
parent | 2dbf36e3c1301f86dbccf22d68956d23771f5b6b (diff) |
BEP: Correctly report test exit code.
When a test failure occurred the BEP would still report a build_finished event
with exit code SUCCESS, even though bazel's exit code was TESTS_FAILED. This is
because we would rely on the exit code reported by the BuildCompleteEvent. However,
this exit code contains only the build status without taking into account the test status.
In this change we introduce the TestingCompleteEvent that reports bazel's final
exit code in case of "bazel test".
RELNOTES: None.
PiperOrigin-RevId: 157445808
Diffstat (limited to 'src/test/java/com/google/devtools/build/lib/syntax/FunctionTest.java')
0 files changed, 0 insertions, 0 deletions