Increase timeout for flaky tests for ProcessThreadImpl

Increase timeout for flaky tests for ProcessThreadImpl

These tests were waiting for a thread to start in 100 ms. This seems to
be not enough on some Windows bots, as there were multiple failures
recently:
https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/9188/steps/modules_unittests/logs/stdio
https://build.chromium.org/p/client.webrtc/builders/Win64%20Debug/builds/8794/steps/modules_unittests/logs/stdio

I have increased the timeout to 500 ms. This will not make successful
test runs slower, but will reduce the chance of a spurious failure.

R=perkj@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/b460fd8b1678a7a705148692fba15613a12d9061

[skvlad, 2016-09-03 00:24:50]

skvlad@webrtc.org changed reviewers:
+ mflodman@webrtc.org, perkj@webrtc.org

[perkj_webrtc, 2016-09-04 13:05:16]

lgtm

[skvlad, 2016-09-06 17:32:04]

The CQ bit was checked by skvlad@webrtc.org

[commit-bot: I haz the power, 2016-09-06 17:32:10]

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

[commit-bot: I haz the power, 2016-09-06 19:32:37]

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

[commit-bot: I haz the power, 2016-09-06 19:32:38]

Try jobs failed on following builders:
  linux_baremetal on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[commit-bot: I haz the power, 2016-09-06 21:34:43]

Description was changed from

==========
Increase timeout for flaky tests for ProcessThreadImpl

These tests were waiting for a thread to start in 100 ms. This seems to
be not enough on some Windows bots, as there were multiple failures
recently:
https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/9188...
https://build.chromium.org/p/client.webrtc/builders/Win64%20Debug/builds/8794...

I have increased the timeout to 500 ms. This will not make successful
test runs slower, but will reduce the chance of a spurious failure.
==========

to

==========
Increase timeout for flaky tests for ProcessThreadImpl

These tests were waiting for a thread to start in 100 ms. This seems to
be not enough on some Windows bots, as there were multiple failures
recently:
https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/9188...
https://build.chromium.org/p/client.webrtc/builders/Win64%20Debug/builds/8794...

I have increased the timeout to 500 ms. This will not make successful
test runs slower, but will reduce the chance of a spurious failure.

R=perkj@webrtc.org

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

[commit-bot: I haz the power, 2016-09-06 21:34:44]

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

[skvlad, 2016-09-06 21:34:45]

Description was changed from

==========
Increase timeout for flaky tests for ProcessThreadImpl

These tests were waiting for a thread to start in 100 ms. This seems to
be not enough on some Windows bots, as there were multiple failures
recently:
https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/9188...
https://build.chromium.org/p/client.webrtc/builders/Win64%20Debug/builds/8794...

I have increased the timeout to 500 ms. This will not make successful
test runs slower, but will reduce the chance of a spurious failure.

R=perkj@webrtc.org

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

to

==========
Increase timeout for flaky tests for ProcessThreadImpl

These tests were waiting for a thread to start in 100 ms. This seems to
be not enough on some Windows bots, as there were multiple failures
recently:
https://build.chromium.org/p/client.webrtc/builders/Win32%20Debug/builds/9188...
https://build.chromium.org/p/client.webrtc/builders/Win64%20Debug/builds/8794...

I have increased the timeout to 500 ms. This will not make successful
test runs slower, but will reduce the chance of a spurious failure.

R=perkj@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/b460fd8b1678a7a705148692f...
==========

[skvlad, 2016-09-06 21:34:46]

Committed patchset #1 (id:1) manually as
b460fd8b1678a7a705148692fba15613a12d9061 (presubmit successful).