diff options
author | Roland Levillain <rpl@google.com> | 2016-11-09 16:38:42 +0000 |
---|---|---|
committer | Roland Levillain <rpl@google.com> | 2016-11-09 16:59:01 +0000 |
commit | 984b0813dfa4451f837720483213ddb963d78b09 (patch) | |
tree | 8ce80392185871694a9a35db7518d53fa68e310b /test/008-exceptions/src/MultiDexBadInitWrapper1.java | |
parent | b4e4c279a0d96c5c9bd6d038d97c3c9992ff8d09 (diff) |
Have `make` report a failing gtest run as a top-level target.
Before, if an individual gtest such (as
`test-art-host-gtest-output_stream_test64`) was invoked as
`make`'s top-level target and failing, `make` would not
report it as such through its exit status (it would be 0
whatever the result). However, when run as part of a
compound test target (such as
`test-art-host-gtest-output_stream_test` or
`test-art-host-gtest`), `make` would actually report this
test's (and maybe others') failure with a non-zero exit
status. This CL forces `make` to report a non-zero exit
status in the former case without breaking the latter one.
Test: Amend a gtest such as compiler/linker/output_stream_test.cc
to make it artificially fail, and run it with:
make test-art-host-gtest-output_stream_test
make test-art-host-gtest-output_stream_test64
Bug: 31755702
Change-Id: Icbb6fef592f14d73808576e7fcb0e9d7079ec9a2
Diffstat (limited to 'test/008-exceptions/src/MultiDexBadInitWrapper1.java')
0 files changed, 0 insertions, 0 deletions