forked from OSchip/llvm-project
c4b7e0125f
The test was failing on Windows machines which had bash.exe on PATH (but not in the so called lit tools dir, containing cmp.exe, grep.exe etc.). The problem was that the outer lit invocation would load LLVMConfig from utils/lit/lit/llvm/config.py, which looks up the tools path with getToolsPath(). That has a surprising side effect of also setting bashPath, in our case setting it to empty. The outer lit invocation would thus configure the pdbg0 and pdbg1 substitutions based on not running with bash. But the inner lit invocation would not load LLVMConfig, so bash would be found on PATH, that would be used as external shell, and so the output wouldn't match pdbg0 and pdbg1. It seems weird to me that getBashPath() will return different results depending on whether getToolsPath() has been called before, but I also don't know how to fix it properly. This commit just relaxes the test case, because there doesn't seem to be much point in testing for the exact syntax of the run file as long as it works. (See https://crbug.com/850023) llvm-svn: 334100 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| unit | ||
| .coveragerc | ||
| boolean-parsing.py | ||
| discovery.py | ||
| googletest-format.py | ||
| googletest-timeout.py | ||
| googletest-upstream-format.py | ||
| lit.cfg | ||
| lit.site.cfg.in | ||
| max-failures.py | ||
| progress-bar.py | ||
| selecting.py | ||
| shell-parsing.py | ||
| shtest-encoding.py | ||
| shtest-format.py | ||
| shtest-output-printing.py | ||
| shtest-run-at-line.py | ||
| shtest-shell.py | ||
| shtest-timeout.py | ||
| shtest-xunit-output.py | ||
| test-data-micro.py | ||
| test-data.py | ||
| test-output-micro.py | ||
| test-output.py | ||
| unittest-adaptor.py | ||
| usage.py | ||
| xunit-output.py | ||