Make context_lost test more of a stress test.

Make context_lost test more of a stress test.

This change much more reliably catches the assertion failure in Issue 365904.

BUG=365904
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=265833

[Ken Russell (switch to Gerrit), 2014-04-23 22:49:44]

Please review. Thanks.

[Zhenyao Mo, 2014-04-23 23:32:51]

On 2014/04/23 22:49:44, Ken Russell wrote:
> Please review. Thanks.

LGTM

[bajones, 2014-04-23 23:34:15]

lgtm

[Ken Russell (switch to Gerrit), 2014-04-24 00:04:17]

The CQ bit was checked by kbr@chromium.org

[commit-bot: I haz the power, 2014-04-24 00:05:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kbr@chromium.org/256433003/1

[commit-bot: I haz the power, 2014-04-24 03:30:06]

Change committed as 265833

[dshwang, 2014-04-24 08:05:59]

On 2014/04/24 03:30:06, I haz the power (commit-bot) wrote:
> Change committed as 265833

After this CL, linux_gpu_triggered_tests becomes flaky;
http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...
Interestingly, only linux_gpu is flaky.

[dshwang, 2014-04-24 08:22:57]

On 2014/04/24 08:05:59, dshwang wrote:
> On 2014/04/24 03:30:06, I haz the power (commit-bot) wrote:
> > Change committed as 265833
> 
> After this CL, linux_gpu_triggered_tests becomes flaky;
>
http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...
> Interestingly, only linux_gpu is flaky.

After https://codereview.chromium.org/254453002/, it is fixed.