[libcxx-commits] [PATCH] D97452: [libcxx] [test] Pass some windows environment variables through to test processes
Louis Dionne via Phabricator via libcxx-commits
libcxx-commits at lists.llvm.org
Tue Mar 2 09:38:28 PST 2021
ldionne requested changes to this revision.
ldionne added a comment.
This revision now requires changes to proceed.
In D97452#2587362 <https://reviews.llvm.org/D97452#2587362>, @mstorsjo wrote:
> In D97452#2587321 <https://reviews.llvm.org/D97452#2587321>, @curdeius wrote:
>> LGTM. But I believe that the long term solution is to run all the tests in the internal lit shell.
> Yes, but I believe that aspect is orthogonal to this script. Currently the lit test driver runs the test script (which consists of two lines, one "clang++" to compile the test and one which invokes the run.py script with python to execute the built test executable) with bash, which maybe could/should be changed to use the lit internal shell. That still keeps the run.py wrapper script for all the purposes it serves right now (codesign, setting up other test specific env variables etc).
Yes, that's correct.
I think it's pretty important to keep `run.py` and the other executors free of logic. Instead, we could string those environment variables into `self.exec_env` in `config.py`. They would then be passed to the executor using the `--env` argument, which was meant for that. WDYT?
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
More information about the libcxx-commits