81c0d36a18
Currently, a LIT test named directly (on the command line) will be run even if the name of the test file does not meet the rules to be considered a test in the LIT test configuration files for its test suite. For example, if the test does not have a recognised file extension. This makes it relatively easy to write a LIT test that won't actually be run. I did in: https://reviews.llvm.org/D82567 This patch adds an error to avoid users doing that. There is a small performance overhead for this check. A command line option has been added so that users can opt into the old behaviour. Differential Revision: https://reviews.llvm.org/D83069 |
||
|---|---|---|
| .. | ||
| allow-retries | ||
| config-map-discovery | ||
| custom-result-category | ||
| discovery | ||
| exec-discovery | ||
| exec-discovery-in-tree | ||
| fake-externals | ||
| googletest-discovery-failed | ||
| googletest-format | ||
| googletest-timeout | ||
| googletest-upstream-format | ||
| lit-opts | ||
| max-failures | ||
| max-time | ||
| parallelism-groups | ||
| progress-bar | ||
| py-config-discovery | ||
| show-result-codes | ||
| show-used-features | ||
| shtest-env | ||
| shtest-format | ||
| shtest-format-argv0 | ||
| shtest-inject | ||
| shtest-keyword-parse-errors | ||
| shtest-not | ||
| shtest-output-printing | ||
| shtest-recursive-substitution | ||
| shtest-run-at-line | ||
| shtest-shell | ||
| shtest-timeout | ||
| test-data | ||
| test-data-micro | ||
| test_retry_attempts | ||
| testrunner-custom-parsers | ||
| unittest-adaptor | ||
| unparsed-requirements | ||
| xunit-output | ||
| lit.cfg | ||