From cd5cd7d14c7ab0a24d40dc3e6588dc817565392c Mon Sep 17 00:00:00 2001 From: Jonas Devlieghere Date: Fri, 4 Oct 2019 22:21:35 +0000 Subject: [PATCH] [test] Run TestLaunchWithShellExpand with /bin/sh on POSIX. Now that we do shell expansion on POSIX with the user's shel, this test can potentially fail. This should ensure that we always use /bin/sh. llvm-svn: 373804 --- .../process/launch-with-shellexpand/TestLaunchWithShellExpand.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lldb/packages/Python/lldbsuite/test/commands/process/launch-with-shellexpand/TestLaunchWithShellExpand.py b/lldb/packages/Python/lldbsuite/test/commands/process/launch-with-shellexpand/TestLaunchWithShellExpand.py index 1ba8121..64a2894 100644 --- a/lldb/packages/Python/lldbsuite/test/commands/process/launch-with-shellexpand/TestLaunchWithShellExpand.py +++ b/lldb/packages/Python/lldbsuite/test/commands/process/launch-with-shellexpand/TestLaunchWithShellExpand.py @@ -2,6 +2,7 @@ Test that argdumper is a viable launching strategy. """ from __future__ import print_function +import os import lldb @@ -36,6 +37,9 @@ class LaunchWithShellExpandTestCase(TestBase): 'break here', lldb.SBFileSpec("main.cpp", False)) self.assertTrue(breakpoint, VALID_BREAKPOINT) + # Ensure we do the expansion with /bin/sh on POSIX. + os.environ["SHELL"] = '/bin/sh' + self.runCmd( "process launch -X true -w %s -- fi*.tx? () > <" % (self.getSourceDir())) -- 2.7.4