remote_run: Don't turn remote_run_result purple on exception

remote_run: Don't turn remote_run_result purple on exception

The linked bug below is the only one I could find on a quick search,
but many people have expressed confusion to me about this.

BUG=642151

[martiniss, 2016-08-30 22:35:44]

Description was changed from

==========
remote_run: Don't turn remote_run_result purple on exception

BUG=642151
==========

to

==========
remote_run: Don't turn remote_run_result purple on exception

The linked bug below is the only one I could find on a quick search,
but many people have expressed confusion to me about this.

BUG=642151
==========

[martiniss, 2016-08-30 22:35:45]

martiniss@chromium.org changed reviewers:
+ iannucci@chromium.org, phajdan.jr@chromium.org

[martiniss, 2016-08-30 22:35:48]

PTAL

[Paweł Hajdan Jr., 2016-08-31 09:23:57]

Well, technically you'd probably want to revert all of
https://codereview.chromium.org/2133573004 , right?

I think this may need more discussion.

This step is confusing no doubt. However, do we have a better way to ensure a
failure in recipe engine always propagates as infra failure to buildbot
otherwise? I'm specifically referring to e.g. recipe engine crashing before we
run any recipe code and similar scenarios.

Of course the build will still result in failure because of non-zero exit code.
However, it'd be red not purple - obscuring the fact of infra failure.

Given the pushback against alerting on anything but infra failures, such change
may limit our ability to react to infra issues with remote_run.