[compiler] Remove deprecated CompilationJob status.

[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org

Committed: https://crrev.com/a1cd3cc8aa703e3bd21b380006b37b9f0229d63c
Cr-Commit-Position: refs/heads/master@{#35834}

[Michael Starzinger, 2016-04-27 17:27:27]

mstarzinger@chromium.org changed reviewers:
+ ahaas@chromium.org

[Michael Starzinger, 2016-04-27 17:27:27]

Benedikt: PTAL.
Andreas: FYI.

[Michael Starzinger, 2016-04-27 17:28:44]

Description was changed from

==========
[compiler] Remove deprecated CompilationJob status.

The distinction between FAILED and BAILED_OUT only distinguishes between
whether an exception is pending or not. Such a dinstinction is obsolete
by now as all callers check for pending exceptions directly. Also it is
impossible for any concurrent part of the job to actually set a pending
exception, hence even the assertion that the concurrent part does not
return FAILED is obsolete.

R=bmeurer@chromium.org
==========

to

==========
[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org
==========

[Benedikt Meurer, 2016-04-27 17:38:17]

lgtm

[Michael Starzinger, 2016-04-27 18:36:29]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-04-27 18:36:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1926693003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1926693003/1

[commit-bot: I haz the power, 2016-04-27 18:38:41]

Description was changed from

==========
[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org
==========

to

==========
[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org
==========

[commit-bot: I haz the power, 2016-04-27 18:38:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-01 22:01:29]

Description was changed from

==========
[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org
==========

to

==========
[compiler] Remove deprecated CompilationJob status.

The status FAILED and BAILED_OUT only distinguishes between whether an
exception is pending or not. Such a distinction is obsolete by now as
all callers check for pending exceptions directly. Also it is impossible
for any concurrent part of the job to actually set a pending exception,
hence even the assertion that the concurrent part does not return FAILED
is obsolete.

R=bmeurer@chromium.org

Committed: https://crrev.com/a1cd3cc8aa703e3bd21b380006b37b9f0229d63c
Cr-Commit-Position: refs/heads/master@{#35834}
==========

[commit-bot: I haz the power, 2016-05-01 22:01:30]

Patchset 1 (id:??) landed as
https://crrev.com/a1cd3cc8aa703e3bd21b380006b37b9f0229d63c
Cr-Commit-Position: refs/heads/master@{#35834}