*** 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, 8 insertions, 7 deletions

diff --git a/lldb/third_party/Python/module/pexpect-2.4/examples/uptime.py b/lldb/third_party/Python/module/pexpect-2.4/examples/uptime.py
index f5018dfe0c1..65cfc6cd711 100644
--- a/lldb/third_party/Python/module/pexpect-2.4/examples/uptime.py
+++ b/lldb/third_party/Python/module/pexpect-2.4/examples/uptime.py
@@ -29,29 +29,30 @@ import re
 #  6:08PM  up 4 days, 22:26, 1 user, load averages: 0.13, 0.09, 0.08
 
 # This parses uptime output into the major groups using regex group matching.
-p = pexpect.spawn ('uptime')
-p.expect('up\s+(.*?),\s+([0-9]+) users?,\s+load averages?: ([0-9]+\.[0-9][0-9]),?\s+([0-9]+\.[0-9][0-9]),?\s+([0-9]+\.[0-9][0-9])')
+p = pexpect.spawn('uptime')
+p.expect(
+    'up\s+(.*?),\s+([0-9]+) users?,\s+load averages?: ([0-9]+\.[0-9][0-9]),?\s+([0-9]+\.[0-9][0-9]),?\s+([0-9]+\.[0-9][0-9])')
 duration, users, av1, av5, av15 = p.match.groups()
 
 # The duration is a little harder to parse because of all the different
 # styles of uptime. I'm sure there is a way to do this all at once with
 # one single regex, but I bet it would be hard to read and maintain.
-# If anyone wants to send me a version using a single regex I'd be happy to see it.
+# If anyone wants to send me a version using a single regex I'd be happy
+# to see it.
 days = '0'
 hours = '0'
 mins = '0'
 if 'day' in duration:
-    p.match = re.search('([0-9]+)\s+day',duration)
+    p.match = re.search('([0-9]+)\s+day', duration)
     days = str(int(p.match.group(1)))
 if ':' in duration:
-    p.match = re.search('([0-9]+):([0-9]+)',duration)
+    p.match = re.search('([0-9]+):([0-9]+)', duration)
     hours = str(int(p.match.group(1)))
     mins = str(int(p.match.group(2)))
 if 'min' in duration:
-    p.match = re.search('([0-9]+)\s+min',duration)
+    p.match = re.search('([0-9]+)\s+min', duration)
     mins = str(int(p.match.group(1)))
 
 # Print the parsed fields in CSV format.
 print 'days, hours, minutes, users, cpu avg 1 min, cpu avg 5 min, cpu avg 15 min'
 print '%s, %s, %s, %s, %s, %s, %s' % (days, hours, mins, users, av1, av5, av15)
-