If the user has a custom PYTHONPATH set, include it in the testing environment. This fixes an issue where certain python packages (pygments, for example) are found during build configuration but then aren't found during testing, leading to test failures.
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
If we do this, should we do it in lit? Else we probably need to do it in llvm, clang, lld, clang-tools-extra, etc etc etc.
Comment Actions
Maybe? I did just enough to get tests working for us. It would be helpful to get this merged before tackling the larger lit question.
Comment Actions
I'd rather have it here than in lit. As a test environment, I love it when there's as few environment values that depends on the launch site as possible. It makes reproducibility easier.