*** This commit represents a complete reformatting of the LLDB source code

*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751

1 files changed, 19 insertions, 10 deletions

diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/tty/TestTerminal.py b/lldb/packages/Python/lldbsuite/test/functionalities/tty/TestTerminal.py
index cebba1b4c57..f4268f5bfa9 100644
--- a/lldb/packages/Python/lldbsuite/test/functionalities/tty/TestTerminal.py
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/tty/TestTerminal.py
@@ -5,14 +5,15 @@ Test lldb command aliases.
 from __future__ import print_function
 
 
-
 import unittest2
-import os, time
+import os
+import time
 import lldb
 from lldbsuite.test.decorators import *
 from lldbsuite.test.lldbtest import *
 from lldbsuite.test import lldbutil
 
+
 class LaunchInTerminalTestCase(TestBase):
 
     mydir = TestBase.compute_mydir(__file__)
@@ -24,18 +25,26 @@ class LaunchInTerminalTestCase(TestBase):
     @expectedFailureDarwin("llvm.org/pr25484")
     # If the test is being run under sudo, the spawned terminal won't retain that elevated
     # privilege so it can't open the socket to talk back to the test case
-    @unittest2.skipIf(hasattr(os, 'geteuid') and os.geteuid() == 0, "test cannot be run as root")
+    @unittest2.skipIf(hasattr(os, 'geteuid') and os.geteuid()
+                      == 0, "test cannot be run as root")
     # Do we need to disable this test if the testsuite is being run on a remote system?
-    # This env var is only defined when the shell is running in a local mac terminal window
-    @unittest2.skipUnless('TERM_PROGRAM' in os.environ, "test must be run on local system")
+    # This env var is only defined when the shell is running in a local mac
+    # terminal window
+    @unittest2.skipUnless(
+        'TERM_PROGRAM' in os.environ,
+        "test must be run on local system")
     @no_debug_info_test
-    def test_launch_in_terminal (self):
+    def test_launch_in_terminal(self):
         exe = "/bin/ls"
         target = self.dbg.CreateTarget(exe)
         launch_info = lldb.SBLaunchInfo(["-lAF", "/tmp/"])
-        launch_info.SetLaunchFlags(lldb.eLaunchFlagLaunchInTTY | lldb.eLaunchFlagCloseTTYOnExit)
+        launch_info.SetLaunchFlags(
+            lldb.eLaunchFlagLaunchInTTY | lldb.eLaunchFlagCloseTTYOnExit)
         error = lldb.SBError()
-        process = target.Launch (launch_info, error)
-        self.assertTrue(error.Success(), "Make sure launch happened successfully in a terminal window")
-        # Running in synchronous mode our process should have run and already exited by the time target.Launch() returns
+        process = target.Launch(launch_info, error)
+        self.assertTrue(
+            error.Success(),
+            "Make sure launch happened successfully in a terminal window")
+        # Running in synchronous mode our process should have run and already
+        # exited by the time target.Launch() returns
         self.assertTrue(process.GetState() == lldb.eStateExited)