llvm-project.git/lldb/test/Shell/Host/TestCustomShell.test, branch main Unnamed repository; edit this file 'description' to name the repository. [LLDB] Fix tests that fail when using internal shell. (#156931) 2025-09-04T17:43:09+00:00 cmtice cmtice@google.com 2025-09-04T17:43:09+00:00 e6aefbec782dbb57f72eb0ae399ed944fe49db2e These tests were failing on darwin, because the internal shell needs environment var definitions to start with 'env'. This PR (hopefully) fixes that problem. 
These tests were failing on darwin, because the internal shell needs
environment var definitions to start with 'env'. This PR (hopefully)
fixes that problem.
 Adapt TestCustomShell and TestMultipleDebuggers to run under ASAN 2023-02-11T01:19:21+00:00 Augusto Noronha augusto2112@me.com 2023-02-10T19:21:14+00:00 294ca122956f78aef3ab4e81108b69518e353b07 In situations where only LLDB is ASANified, a false positive occurs unless ASAN_OPTIONS=detect_container_overflow=0 is set in the environment. Differential Revision: https://reviews.llvm.org/D143772 
In situations where only LLDB is ASANified, a false positive occurs
unless ASAN_OPTIONS=detect_container_overflow=0 is set in the
environment.

Differential Revision: https://reviews.llvm.org/D143772
Don't depend on the "run" alias doing shell expanding. 2021-06-15T23:37:46+00:00 Jim Ingham jingham@apple.com 2021-06-15T23:35:44+00:00 80b2da42d28466341b9512599aac354c178c39f8 Instead dial it up explicitly. This test started failing recently and I'm not sure why. It also doesn't make sense to me the replacing "run" with "process launch -X 1 --" should make any difference - run is an alias for the latter. But it does pass with the change, and unless we are testing for the exact run alias, it's better to ask for what we want explicitly. 
Instead dial it up explicitly.

This test started failing recently and I'm not sure why.  It also
doesn't make sense to me the replacing "run" with "process launch -X 1 --"
should make any difference - run is an alias for the latter.  But
it does pass with the change, and unless we are testing for the exact
run alias, it's better to ask for what we want explicitly.
[lldb] Fix 'r' and 'run' aliases on Apple Silicon 2021-02-12T04:23:53+00:00 Jonas Devlieghere jonas@devlieghere.com 2021-02-12T04:20:04+00:00 4d3a061c32ee5c4fb88be389a4dd7fd71fc9fa9c The 'r' and 'run' aliases were different based on the target architecture. I suspect the intention was to disable shell expansion on embedded devices. This fixes TestCustomShell.test on AS. 
The 'r' and 'run' aliases were different based on the target
architecture. I suspect the intention was to disable shell expansion on
embedded devices. This fixes TestCustomShell.test on AS.
[lldb/Driver] Exit with a non-zero exit code in case of error in batch mode. 2020-05-05T18:01:44+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-05-05T17:58:03+00:00 61d5b0e66394d61947d61861685b4223214f023e We have the option to stop running commands in batch mode when an error occurs. When that happens we should exit the driver with a non-zero exit code. Differential revision: https://reviews.llvm.org/D78825 
We have the option to stop running commands in batch mode when an error
occurs. When that happens we should exit the driver with a non-zero exit
code.

Differential revision: https://reviews.llvm.org/D78825
[lldb/lit] Introduce %clang_host substitutions 2019-10-31T09:40:37+00:00 Pavel Labath pavel@labath.sk 2019-10-30T14:57:16+00:00 9c739252261ea762d1bbbd8234d93c9038711fcd Summary: This patch addresses an ambiguity in how our existing tests invoke the compiler. Roughly two thirds of our current "shell" tests invoke the compiler to build the executables for the host. However, there is also a significant number of tests which don't build a host binary (because they don't need to run it) and instead they hardcode a certain target. We also have code which adds a bunch of default arguments to the %clang substitutions. However, most of these arguments only really make sense for the host compilation. So far, this has worked mostly ok, because the arguments we were adding were not conflicting with the target-hardcoding tests (though they did provoke an occasional "argument unused" warning). However, this started to break down when we wanted to use target-hardcoding clang-cl tests (D69031) because clang-cl has a substantially different command line, and it was getting very confused by some of the arguments we were adding on non-windows hosts. This patch avoid this problem by creating separate %clang(xx,_cl)_host substutitions, which are specifically meant to be used for compiling host binaries. All funny host-specific options are moved there. To ensure that the regular %clang substitutions are not used for compiling host binaries (skipping the extra arguments) I employ a little hac^H^H^Htrick -- I add an invalid --target argument to the %clang substitution, which means that one has to use an explicit --target in order for the compilation to succeed. Reviewers: JDevlieghere, aprantl, mstorsjo, espindola Subscribers: emaste, arichardson, MaskRay, jfb, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D69619 
Summary:
This patch addresses an ambiguity in how our existing tests invoke the
compiler. Roughly two thirds of our current "shell" tests invoke the
compiler to build the executables for the host. However, there is also
a significant number of tests which don't build a host binary (because
they don't need to run it) and instead they hardcode a certain target.

We also have code which adds a bunch of default arguments to the %clang
substitutions. However, most of these arguments only really make sense
for the host compilation. So far, this has worked mostly ok, because the
arguments we were adding were not conflicting with the target-hardcoding
tests (though they did provoke an occasional "argument unused" warning).

However, this started to break down when we wanted to use
target-hardcoding clang-cl tests (D69031) because clang-cl has a
substantially different command line, and it was getting very confused
by some of the arguments we were adding on non-windows hosts.

This patch avoid this problem by creating separate %clang(xx,_cl)_host
substutitions, which are specifically meant to be used for compiling
host binaries. All funny host-specific options are moved there. To
ensure that the regular %clang substitutions are not used for compiling
host binaries (skipping the extra arguments) I employ a little
hac^H^H^Htrick -- I add an invalid --target argument to the %clang
substitution, which means that one has to use an explicit --target in
order for the compilation to succeed.

Reviewers: JDevlieghere, aprantl, mstorsjo, espindola

Subscribers: emaste, arichardson, MaskRay, jfb, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D69619
[lldb] [test] Mark TestCustomShell XFAIL on *bsd as well 2019-10-30T12:26:13+00:00 Michał Górny mgorny@gentoo.org 2019-10-30T12:26:13+00:00 02f4cfecf6936a28cbba9314a9cbb3f510aa9710 All *BSD targets do not implement ShellExpandArguments, so mark the test appropriately. 
All *BSD targets do not implement ShellExpandArguments, so mark
the test appropriately.
Re-land "[test] Split LLDB tests into API, Shell & Unit" 2019-10-09T19:22:02+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-10-09T19:22:02+00:00 87aa9c9e4d41ed881453e2fab85b3d25f648bb55 The original patch got reverted because it broke `check-lldb` on a clean build. This fixes that. llvm-svn: 374201 
The original patch got reverted because it broke `check-lldb` on a clean
build. This fixes that.

llvm-svn: 374201
Revert [test] Split LLDB tests into API, Shell & Unit 2019-10-09T17:35:43+00:00 Adrian Prantl aprantl@apple.com 2019-10-09T17:35:43+00:00 0115c10328281567391855766fef8fbe57a1d4cc as it appears to have broken check-lldb. This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82) llvm-svn: 374187 
as it appears to have broken check-lldb.

This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82)

llvm-svn: 374187
[test] Split LLDB tests into API, Shell & Unit 2019-10-09T16:38:47+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-10-09T16:38:47+00:00 22314179f0660c172514b397060fd8f34b586e82 LLDB has three major testing strategies: unit tests, tests that exercise the SB API though dotest.py and what we currently call lit tests. The later is rather confusing as we're now using lit as the driver for all three types of tests. As most of this grew organically, the directory structure in the LLDB repository doesn't really make this clear. The 'lit' tests are part of the root and among these tests there's a Unit and Suite folder for the unit and dotest-tests. This layout makes it impossible to run just the lit tests. This patch changes the directory layout to match the 3 testing strategies, each with their own directory and their own configuration file. This means there are now 3 directories under lit with 3 corresponding targets: - API (check-lldb-api): Test exercising the SB API. - Shell (check-lldb-shell): Test exercising command line utilities. - Unit (check-lldb-unit): Unit tests. Finally, there's still the `check-lldb` target that runs all three test suites. Finally, this also renames the lit folder to `test` to match the LLVM repository layout. Differential revision: https://reviews.llvm.org/D68606 llvm-svn: 374184 
LLDB has three major testing strategies: unit tests, tests that exercise
the SB API though dotest.py and what we currently call lit tests. The
later is rather confusing as we're now using lit as the driver for all
three types of tests. As most of this grew organically, the directory
structure in the LLDB repository doesn't really make this clear.

The 'lit' tests are part of the root and among these tests there's a
Unit and Suite folder for the unit and dotest-tests. This layout makes
it impossible to run just the lit tests.

This patch changes the directory layout to match the 3 testing
strategies, each with their own directory and their own configuration
file. This means there are now 3 directories under lit with 3
corresponding targets:

 - API (check-lldb-api): Test exercising the SB API.
 - Shell (check-lldb-shell): Test exercising command line utilities.
 - Unit (check-lldb-unit): Unit tests.

Finally, there's still the `check-lldb` target that runs all three test
suites.

Finally, this also renames the lit folder to `test` to match the LLVM
repository layout.

Differential revision: https://reviews.llvm.org/D68606

llvm-svn: 374184