Gracefully handle tests finishing simultanously in 2+ secondary windows.

Gracefully handle tests finishing simultanously in 2+ secondary renderers.

This CL makes the layout tests harness more resiliant against
a situation where testRunner.notifyDone() is called simultaneously in
more than 1 renderer process.  Such situation usually indicates a bug in
the test (e.g. see https://crbug.com/716085#c13), but this shouldn't
cause a crash or other problems in the layout tests harness.

BUG=716085
Review-Url: https://codereview.chromium.org/2852753003
Cr-Commit-Position: refs/heads/master@{#468997}
Committed: https://chromium.googlesource.com/chromium/src/+/2823efd6fec41c2ab4f47d3b241bc6e4330bb3fc

[Łukasz Anforowicz, 2017-04-28 23:29:06]

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

[commit-bot: I haz the power, 2017-04-28 23:29:56]

Dry run: CQ is trying da patch.

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

[Łukasz Anforowicz, 2017-04-29 00:08:08]

lukasza@chromium.org changed reviewers:
+ mkwst@chromium.org

[Łukasz Anforowicz, 2017-04-29 00:08:09]

mkwst@, can you PTAL?

[commit-bot: I haz the power, 2017-04-29 02:49:55]

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

[commit-bot: I haz the power, 2017-04-29 02:49:56]

Dry run: This issue passed the CQ dry run.

[Łukasz Anforowicz, 2017-05-01 16:03:53]

Description was changed from

==========
Gracefully handle tests finishing simultanously in 2+ secondary windows.

BUG=716085
==========

to

==========
Gracefully handle tests finishing simultanously in 2+ secondary renderers.

This CL makes the layout tests harness more resiliant against
a situation where testRunner.notifyDone() is called simultaneously in
more than 1 renderer process.  Such situation usually indicates a bug in
the test (e.g. see https://crbug.com/716085#c13), but this shouldn't
cause a crash or other problems in the layout tests harness.

BUG=716085
==========

[Łukasz Anforowicz, 2017-05-01 16:06:26]

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

[commit-bot: I haz the power, 2017-05-01 16:06:56]

Dry run: 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, 2017-05-01 17:44:27]

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

[commit-bot: I haz the power, 2017-05-01 17:44:28]

Dry run: This issue passed the CQ dry run.

[Mike West, 2017-05-02 07:03:29]

Code change LGTM. Can you add a test for this behavior?

[Łukasz Anforowicz, 2017-05-02 21:38:25]

On 2017/05/02 07:03:29, Mike West wrote:
> Code change LGTM.

Thanks.

> Can you add a test for this behavior?

Done in patchset #3.

[Łukasz Anforowicz, 2017-05-03 00:17:21]

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

[commit-bot: I haz the power, 2017-05-03 00:18:16]

Dry run: 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, 2017-05-03 02:01:02]

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

[commit-bot: I haz the power, 2017-05-03 02:01:03]

Dry run: This issue passed the CQ dry run.

[Mike West, 2017-05-03 07:37:00]

Thanks for the test! LGTM.

[Łukasz Anforowicz, 2017-05-03 16:10:01]

The CQ bit was checked by lukasza@chromium.org

[commit-bot: I haz the power, 2017-05-03 16:10:33]

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, 2017-05-03 16:15:39]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1493827801597580,
"parent_rev": "4c2ed2beb2e324206b2a9011b9fbfa6660e9fc55", "commit_rev":
"2823efd6fec41c2ab4f47d3b241bc6e4330bb3fc"}

[commit-bot: I haz the power, 2017-05-03 16:16:21]

Description was changed from

==========
Gracefully handle tests finishing simultanously in 2+ secondary renderers.

This CL makes the layout tests harness more resiliant against
a situation where testRunner.notifyDone() is called simultaneously in
more than 1 renderer process.  Such situation usually indicates a bug in
the test (e.g. see https://crbug.com/716085#c13), but this shouldn't
cause a crash or other problems in the layout tests harness.

BUG=716085
==========

to

==========
Gracefully handle tests finishing simultanously in 2+ secondary renderers.

This CL makes the layout tests harness more resiliant against
a situation where testRunner.notifyDone() is called simultaneously in
more than 1 renderer process.  Such situation usually indicates a bug in
the test (e.g. see https://crbug.com/716085#c13), but this shouldn't
cause a crash or other problems in the layout tests harness.

BUG=716085

Review-Url: https://codereview.chromium.org/2852753003
Cr-Commit-Position: refs/heads/master@{#468997}
Committed:
https://chromium.googlesource.com/chromium/src/+/2823efd6fec41c2ab4f47d3b241b...
==========

[commit-bot: I haz the power, 2017-05-03 16:16:25]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/2823efd6fec41c2ab4f47d3b241b...