maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/utils/lit/tests/custom-result-category.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

16 lines
484 B
Python
Raw Normal View History

[lit] Disable test on Windows abhinavgaba reported that that the custom-result-category.py test hangs on a Windows build bot [1]. Disable it for now. [1] https://reviews.llvm.org/D78164#2018178
2020-05-05 04:06:56 +08:00
# UNSUPPORTED: system-windows
[lit] Provide extension API for custom result categories The lnt test suite defines custom result codes [1]. Support those via an extension API instead of "by accident", which should offer the advantage of properly handling them when we print test results. [1] https://reviews.llvm.org/D77986 Reviewed By: Meinersbur Differential Revision: https://reviews.llvm.org/D78164
2020-04-15 06:55:38 +08:00
# Test lit.main.add_result_category() extension API.
[llvm] [lit] Support forcing lexical test order Add a new --order option to choose between available test orders: the default "smart" order, predictable "lexical" order or "random" order. Default to using lexical order and one job in the lit test suite. Differential Revision: https://reviews.llvm.org/D107695
2021-08-07 22:40:09 +08:00
# RUN: not %{lit} %{inputs}/custom-result-category | FileCheck %s
[lit] Provide extension API for custom result categories The lnt test suite defines custom result codes [1]. Support those via an extension API instead of "by accident", which should offer the advantage of properly handling them when we print test results. [1] https://reviews.llvm.org/D77986 Reviewed By: Meinersbur Differential Revision: https://reviews.llvm.org/D78164
2020-04-15 06:55:38 +08:00
# CHECK: CUSTOM_PASS: custom-result-category :: test1.txt
# CHECK: CUSTOM_FAILURE: custom-result-category :: test2.txt
[lit] Improve consistency for showing result groups Before this change we showed all result groups with a code that was not explicitly hard-coded set. This set missed the FLAKYPASS result code. Let's generalize the code to always show failures and the additionally requested result codes.
2020-06-17 03:15:16 +08:00
# CHECK-NOT: My Passed Tests (1)
# CHECK-NOT: custom-result-category :: test1.txt
# CHECK: My Failed Tests (1)
# CHECK: custom-result-category :: test2.txt
[lit] Provide extension API for custom result categories The lnt test suite defines custom result codes [1]. Support those via an extension API instead of "by accident", which should offer the advantage of properly handling them when we print test results. [1] https://reviews.llvm.org/D77986 Reviewed By: Meinersbur Differential Revision: https://reviews.llvm.org/D78164
2020-04-15 06:55:38 +08:00
[lit] Improve naming of test result categories Improve consistency when printing test results: Previously we were using different labels for group names (the header for the list of, e.g., failing tests) and summary count lines. For example, "Failing Tests"/"Unexpected Failures". This commit changes lit to label things consistently. Improve wording of labels: When talking about individual test results, the first word in "Unexpected Failures", "Expected Passes", and "Individual Timeouts" is superfluous. Some labels contain the word "Tests" and some don't. Let's simplify the names. Before: ``` Failing Tests (1): ... Expected Passes : 3 Unexpected Failures: 1 ``` After: ``` Failed Tests (1): ... Passed: 3 Failed: 1 ``` Reviewed By: ldionne Differential Revision: https://reviews.llvm.org/D77708
2020-04-08 13:48:39 +08:00
# CHECK: My Passed: 1
# CHECK: My Failed: 1