| commit | c5c1d50051f52745dca109c4695b8115a077a5f0 | [log] [tgz] |
|---|---|---|
| author | Nick Desaulniers <ndesaulniers@google.com> | Thu May 30 11:11:56 2024 -0700 |
| committer | Nick Desaulniers <ndesaulniers@google.com> | Fri May 31 10:08:16 2024 -0700 |
| tree | 0b77cbf3ad7698ef5a09726fad5e49eaf308db9c | |
| parent | ae04d1ce07dddcd0d4caa9d354995245140f719e [diff] |
external: llvm-libc: add --gtest_color=no to TEST_MAPPING llvm-libc's pseudo GTest doesn't support autodetection (--gtest_color=auto), and must be forced off. Otherwise ATest can't parse the output. Use native-test-flag to pass --gtest_color=no to the command line invocation of the test binary. The native-test-flag field's documentation leaves much to be desired. Unfortunately, this will need to be added for every unit test... Test: cd external/llvm-libc && atest :postsubmit Link: https://github.com/llvm/llvm-project/pull/93852 Link: https://source.android.com/docs/core/tests/development/test-mapping#follow_an_example Link: https://source.android.com/docs/core/tests/development/gtest#workflow Bug: 335872118 Change-Id: If4b89e53cb0b843d5c378af0af3c8122d80c6f59