diff options
| author | Yuanfang Chen <yuanfang.chen@sony.com> | 2022-04-12 12:09:34 -0700 |
|---|---|---|
| committer | Yuanfang Chen <yuanfang.chen@sony.com> | 2022-04-12 14:51:12 -0700 |
| commit | cd0a5889d71c62ae7cefc97da6335134c02ef102 (patch) | |
| tree | 69a76a5df6c292e99b4716b06ff2ecc9063b759c /lldb/test/API/python_api/debugger/TestDebuggerAPI.py | |
| parent | 163a9f4552bea71b2d53126a5f74f9a1b47d2865 (diff) | |
[Reland][lit] Use sharding for GoogleTest format
This helps lit unit test performance by a lot, especially on windows. The performance gain comes from launching one gtest executable for many subtests instead of one (this is the current situation).
The shards are executed by the test runner and the results are stored in the
json format supported by the GoogleTest. Later in the test reporting stage,
all test results in the json file are retrieved to continue the test results
summary etc.
On my Win10 desktop, before this patch: `check-clang-unit`: 177s, `check-llvm-unit`: 38s; after this patch: `check-clang-unit`: 37s, `check-llvm-unit`: 11s.
On my Linux machine, before this patch: `check-clang-unit`: 46s, `check-llvm-unit`: 8s; after this patch: `check-clang-unit`: 7s, `check-llvm-unit`: 4s.
Reviewed By: yln, rnk, abrachet
Differential Revision: https://reviews.llvm.org/D122251
Diffstat (limited to 'lldb/test/API/python_api/debugger/TestDebuggerAPI.py')
0 files changed, 0 insertions, 0 deletions