DESCRIPTION

Bug 415710: 'perf' check should explicitly handle a null process.

A null process usually indicates the command could not be found. In
addition, the RuntimeProcessFactory#whichCommand should safely handle an
empty standard output stream without relying on exception catching.

Change-Id: Ifa26f211af8815e8db7a404e856cdb4220a35857


COMMENTS

author: Nathanael Holden
date: 2013-08-28 19:40:23.000000000

Uploaded patch set 4.

-------------------------------------
author: Brenden Conley
date: 2013-08-28 19:40:29.000000000

Patch Set 4:

Build Started https://hudson.eclipse.org/sandbox/job/linuxtools/3309/

-------------------------------------
author: Brenden Conley
date: 2013-08-28 20:00:03.000000000

Patch Set 4: Verified+1

Build Successful 

https://hudson.eclipse.org/sandbox/job/linuxtools/3309/ : SUCCESS

-------------------------------------
author: Kaeden Tapia
date: 2013-08-29 15:30:22.000000000

Patch Set 4: Code-Review+1

Looks good. Thank you!

-------------------------------------
author: Nathanael Holden
date: 2013-08-29 20:30:09.000000000

Patch Set 4: Verified+1 Code-Review+2 IP-Clean+1

Thanks for the review :) I'm pushing this and hope to backport as well to 2.1 given that it's a bug fix.

-------------------------------------
author: Gerrit Code Review
date: 2013-08-29 20:30:10.000000000

The change could not be merged due to a path conflict.

Please rebase the change locally and upload the rebased commit for review.

-------------------------------------
author: Nathanael Holden
date: 2013-08-29 20:30:23.000000000

Patch Set 5: Patch Set 4 was rebased

-------------------------------------
