forked from OSchip/llvm-project
3b3cdcc7a5
Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233 |
||
|---|---|---|
| .. | ||
| 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 | ||