This updates the googletest format to support tests that use GTEST_SKIP(), which is now available with the updated googletest framework.
Details
Diff Detail
Event Timeline
I am not really sure who can review this. If anyone knows the right person, please extend the list.
llvm/utils/lit/tests/googletest-format.py | ||
---|---|---|
25–27 | Is this ordered guaranteed? If not, we should use CHECK-DAG. |
llvm/utils/lit/tests/googletest-format.py | ||
---|---|---|
25–27 | print_summary() in lit/main.py prints them in the exact order as ResultCodes are defined in lit/Test.py, so the sequence is stable. |
llvm/utils/lit/lit/formats/googletest.py | ||
---|---|---|
138 | Looking for this exact string seems fragile. Maybe use a regex that can cope with a variable amount of spaces? |
llvm/utils/lit/lit/formats/googletest.py | ||
---|---|---|
138 | This corresponds to how the framework prints the summary, see PrettyUnitTestResultPrinter::OnTestIterationEnd(). If that is broken in some future release of the framework, we will fix the condition, but before that, we cannot predict in which way the report may be changed, so there is no need to overcomplicate the code. |
Looking for this exact string seems fragile. Maybe use a regex that can cope with a variable amount of spaces?