forked from OSchip/llvm-project
4415678718
Don't produce or expect any output from the infinite looping test - doing so is a recipe for racey flakyness without a longer timeout to ensure the output is received first, even though that doesn't seem integral/important to the test. Instead have a plain, no output infinite loop and check that that is caught and handled. If for some reason the output is valuable for test coverage - the timeout should be increased from 1 second to give the process time to output the text, flush, and for that text to be received and buffered before the test is timed out. |
||
|---|---|---|
| .. | ||
| 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 | ||