Fix breakpoint-command.test when no script interpreter is compiled in.
authorMitch Phillips <31459023+hctim@users.noreply.github.com>
Mon, 12 Dec 2022 22:00:19 +0000 (14:00 -0800)
committerMitch Phillips <31459023+hctim@users.noreply.github.com>
Mon, 12 Dec 2022 22:12:52 +0000 (14:12 -0800)
commit1b753240d50a930c12c42e2f230804db3dccde96
treee4bfd65bb150d640f732633f4d991030a7ee07e6
parent079cd4a52f398ccf4a04cf47f2c3c536a5011585
Fix breakpoint-command.test when no script interpreter is compiled in.

My local build is with -DLLVM_ENABLE_PROJECTS=lldb, but I don't compile
with -DLLDB_ENABLE_PYTHON=True or -DLLDB_ENABLE_LUA=True. This results
in there being no script interpreter.

The test lldb/test/Shell/Breakpoint/breakpoint-command.test has an
implicit dependency on a script interpreter being available.

This patch makes that dependency clear. If you have a script
interpreter, the test gets run, otherwise it gets skipped. This means
that folks (like me) who naively use -DLLVM_ENABLE_PROJECTS=lldb can
continue to run check-all without breakages.

Reviewed By: JDevlieghere

Differential Revision: https://reviews.llvm.org/D139463
lldb/test/Shell/Breakpoint/breakpoint-command.test