Save an early test summary in case the test launcher crashes or gets killed

Save an early test summary in case the test launcher crashes or gets killed

This may turn some infra failures (purple) into INVALID_TEST_RESULTS (red)
in case the test launcher is for example early terminated on swarming.

See bug for more details.

BUG=649831
Committed: https://crrev.com/5dc1ee3fccf13062e1ee9b1fbb25189f617c74c8
Cr-Commit-Position: refs/heads/master@{#424709}

[Paweł Hajdan Jr., 2016-10-11 19:40:30]

The CQ bit was checked by phajdan.jr@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-11 19:41:01]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Paweł Hajdan Jr., 2016-10-11 20:12:07]

phajdan.jr@chromium.org changed reviewers:
+ dpranke@chromium.org, jam@chromium.org

[commit-bot: I haz the power, 2016-10-11 20:42:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-11 20:42:38]

Dry run: This issue passed the CQ dry run.

[Dirk Pranke, 2016-10-11 21:26:11]

Can you update the CL description with more information about what problem this
is solving and why it's useful?

If I'm understanding correctly, what this solves is the problem where there's
never *any* output.json and so all we get is an infra failure reported. However,
we still won't get incremental results for the tests that did complete. Is that
right?

[jam, 2016-10-11 21:26:53]

lgtm

[Paweł Hajdan Jr., 2016-10-12 10:41:09]

Description was changed from

==========
Save an early test summary in case the test launcher crashes or gets killed

BUG=649831
==========

to

==========
Save an early test summary in case the test launcher crashes or gets killed

This may turn some infra failures (purple) into INVALID_TEST_RESULTS (red)
in case the test launcher is for example early terminated on swarming.

See bug for more details.

BUG=649831
==========

[Paweł Hajdan Jr., 2016-10-12 10:41:40]

On 2016/10/11 at 21:26:11, dpranke wrote:
> Can you update the CL description with more information about what problem
this is solving and why it's useful?
> 
> If I'm understanding correctly, what this solves is the problem where there's
never *any* output.json and so all we get is an infra failure reported. However,
we still won't get incremental results for the tests that did complete. Is that
right?

Correct. I updated the description, and more context is in the linked bug.

[Paweł Hajdan Jr., 2016-10-12 10:41:45]

The CQ bit was checked by phajdan.jr@chromium.org

[commit-bot: I haz the power, 2016-10-12 10:41:59]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-12 10:46:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-12 10:47:59]

Description was changed from

==========
Save an early test summary in case the test launcher crashes or gets killed

This may turn some infra failures (purple) into INVALID_TEST_RESULTS (red)
in case the test launcher is for example early terminated on swarming.

See bug for more details.

BUG=649831
==========

to

==========
Save an early test summary in case the test launcher crashes or gets killed

This may turn some infra failures (purple) into INVALID_TEST_RESULTS (red)
in case the test launcher is for example early terminated on swarming.

See bug for more details.

BUG=649831

Committed: https://crrev.com/5dc1ee3fccf13062e1ee9b1fbb25189f617c74c8
Cr-Commit-Position: refs/heads/master@{#424709}
==========

[commit-bot: I haz the power, 2016-10-12 10:48:00]

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