Change drmemory_analyze to print reports and suppressions to stdout

Change drmemory_analyze to print reports and suppressions to stdout
This way it should be processed by the gtest_command log parser
(looks like it doesn't look into stderr...)

TBR=bruening

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

[commit-bot: I haz the power, 2011-12-01 13:59:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/timurrrr@chromium.org/8770007/1

[commit-bot: I haz the power, 2011-12-01 15:04:34]

Change committed as 112464

[Derek Bruening, 2011-12-01 15:41:31]

> This way it should be processed by the gtest_command log parser

No idea what implications this has or what problem it's fixing.  Who is using
the "gtest_command log parser" and why wasn't this a problem in the past?

[Timur Iskhodzhanov, 2011-12-01 17:19:29]

On 2011/12/01 15:41:31, Derek Bruening wrote:
> > This way it should be processed by the gtest_command log parser
> 
> No idea what implications this has or what problem it's fixing.
Problem: the buildbot was not seeing the generated suppressions.
Compare the list of sql results:
before
http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20%28DrMemo...
after
http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20%28DrMemo...

> Who is using the "gtest_command log parser"
It's the log parser on the buildbot which extracts the generated suppressions
and shows their hashes in the list of failures 

> and why wasn't this a problem in the past?
a) looks like the POSIX bots have stderr merged with stdout.
  This is not the case for the Windows bots. 
b) looks like log parser only watches the stdout part.
  As a result, it wasn't seeing the DrMemory reports.

As a long-term solution we might tweak the log parser to read stderr too, but
I'm not sure
a) it's really needed
b) it's trivial (other parts of the log parser may not want to see stderr)

[Derek Bruening, 2011-12-01 17:33:36]

On 2011/12/01 17:19:29, Timur Iskhodzhanov wrote:
> On 2011/12/01 15:41:31, Derek Bruening wrote:
> > > This way it should be processed by the gtest_command log parser
> > 
> > No idea what implications this has or what problem it's fixing.
> Problem: the buildbot was not seeing the generated suppressions.
> Compare the list of sql results:
> before
>
http://build.chromium.org/p/chromium.fyi/builders/Windows%2520Tests%2520%2528...
> after
>
http://build.chromium.org/p/chromium.fyi/builders/Windows%2520Tests%2520%2528...
> 
> > Who is using the "gtest_command log parser"
> It's the log parser on the buildbot which extracts the generated suppressions
> and shows their hashes in the list of failures 
> 
> > and why wasn't this a problem in the past?
> a) looks like the POSIX bots have stderr merged with stdout.
>   This is not the case for the Windows bots. 
> b) looks like log parser only watches the stdout part.
>   As a result, it wasn't seeing the DrMemory reports.
> 
> As a long-term solution we might tweak the log parser to read stderr too, but
> I'm not sure
> a) it's really needed
> b) it's trivial (other parts of the log parser may not want to see stderr)

OK, thanks for the explanation.

[Derek Bruening, 2011-12-01 17:34:02]

LGTM