Check in a quick sed script to reduce Mac build logs.

Check in a quick sed script to reduce Mac build logs.

This strips out most of the command lines, making it look a little
more like the Linux output.

TEST=download mac build output;
  ./build/sanitize-mac-build-log.sed < build-output
  and verify it is shorter

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=69027

[Mark Mentovai, 2010-12-10 22:36:18]

http://codereview.chromium.org/5678006/diff/1/build/sanitize-mac-build-log.sed
File build/sanitize-mac-build-log.sed (right):

http://codereview.chromium.org/5678006/diff/1/build/sanitize-mac-build-log.se...
build/sanitize-mac-build-log.sed:14: \|^    /Developer/usr/bin/g++|d
I think Xcode always invokes gcc (with -x) when distcc is not in use, and never
g++. That’s important to catch people who aren’t building distributed.

http://codereview.chromium.org/5678006/diff/1/build/sanitize-mac-build-log.se...
build/sanitize-mac-build-log.sed:16: s|^Distributed-CompileC \(.*\) normal i386
c++ com.apple.compilers.gcc.4_2|CC \1|
Match without Distributed- too, for the same reason.

[evanm, 2010-12-10 22:51:24]

On 2010/12/10 22:36:18, Mark Mentovai wrote:
>
http://codereview.chromium.org/5678006/diff/1/build/sanitize-mac-build-log.se...
> build/sanitize-mac-build-log.sed:14: \|^    /Developer/usr/bin/g++|d
> I think Xcode always invokes gcc (with -x) when distcc is not in use, and
never
> g++. That’s important to catch people who aren’t building distributed.

I guess if you're building locally, Xcode knows how to trim this output already.
 I'm more interested in the bots.

>
http://codereview.chromium.org/5678006/diff/1/build/sanitize-mac-build-log.se...
> build/sanitize-mac-build-log.sed:16: s|^Distributed-CompileC \(.*\) normal
i386
> c++ com.apple.compilers.gcc.4_2|CC \1|
> Match without Distributed- too, for the same reason.

It appears both options of
 /\(Distributed-\)\?CompileC/
 /\(Distributed-\|\)CompileC/
are GNU extensions to sed, so I'll just copy'n'paste.

[Mark Mentovai, 2010-12-10 22:54:07]

Evan wrote:
> I guess if you're building locally, Xcode knows how to trim this output
> already.  I'm more interested in the bots.

Xcode doesn’t know jack!

There’s no difference between the xcodebuild we run on the bots and
the xcodebuild people run locally.

If you’re running via the UI, Xcode will format things nicely for you,
but that won’t help command-line jockeys.

Anyway, as bots are brought up and troubleshot and kicked around and
other things happen, we don’t really have a guarantee that distcc will
always be on.

[Evan Martin, 2010-12-13 18:50:58]

My last mail was intended to indicate PTAL but it wasn't clear.  So: PTAL

[Mark Mentovai, 2010-12-13 18:54:13]

LGTM

http://codereview.chromium.org/5678006/diff/3002/build/sanitize-mac-build-log...
File build/sanitize-mac-build-log.sed (right):

http://codereview.chromium.org/5678006/diff/3002/build/sanitize-mac-build-log...
build/sanitize-mac-build-log.sed:2: 
Give me some stupid boilerplate lice.

Also, make sure the file gets checked in with the proper svn:eol-style.