diff options
| author | Joel E. Denny <jdenny.ornl@gmail.com> | 2023-09-19 12:46:37 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-09-19 12:46:37 -0400 |
| commit | fba457d77e59bff91fe3e01dcaec6cf3d2b5b556 (patch) | |
| tree | 314406406091d1ede11ff43ea41434225a891e33 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h | |
| parent | f223022a4c521296a6d058862d66443ab9e355bf (diff) | |
| download | llvm-fba457d77e59bff91fe3e01dcaec6cf3d2b5b556.zip llvm-fba457d77e59bff91fe3e01dcaec6cf3d2b5b556.tar.gz llvm-fba457d77e59bff91fe3e01dcaec6cf3d2b5b556.tar.bz2 | |
[lit] Echo full RUN lines in case of external shells (#66408)
Before <https://reviews.llvm.org/D154984> and
<https://reviews.llvm.org/D156954>, lit reported full RUN lines in a
`Script:` section. Now, in the case of lit's internal shell, it's the
execution trace that includes them. However, if lit is configured to use
an external shell (e.g., bash, windows `cmd`), they aren't reported at
all.
A fix was requested at the following:
* <https://reviews.llvm.org/D154984#4627605>
*
<https://discourse.llvm.org/t/rfc-improving-lits-debug-output/72839/35?u=jdenny-ornl>
This patch does not address the case when the external shell is windows
`cmd`. As discussed at
<https://github.com/llvm/llvm-project/pull/65242>, it's not clear
whether that's a use case that people still care about, and it seems to
be generally broken anyway.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions