For certain record_wpr unittests, use --browser flag.

For certain record_wpr unittests, use --browser flag.

Some of the record_wpr unittests are causing issues. By passing in the --browser
flag with the existing browser_type for these tests, we should be able to avoid
this flakiness (caused by waiting for another browser to finish launching).

BUG=424439
Committed: https://crrev.com/fd0beb29644013f310edda3efaf162c43c9cee59
Cr-Commit-Position: refs/heads/master@{#300045}

[ariblue, 2014-10-17 01:36:06]

ariblue@google.com changed reviewers:
+ dtu@chromium.org, tonyg@chromium.org

[tonyg, 2014-10-17 01:38:16]

This makes sense, but can't you define issues a little better in the CL
description? Is this the reason I had to roll back that ephemeral port change
this morning?

[tonyg, 2014-10-17 01:38:46]

On 2014/10/17 01:38:16, tonyg wrote:
> This makes sense, but can't you define issues a little better in the CL
> description? Is this the reason I had to roll back that ephemeral port change
> this morning?

Or maybe just associate it with a bug.

lgtm

[ariblue, 2014-10-17 01:58:13]

On 2014/10/17 01:38:46, tonyg wrote:
> On 2014/10/17 01:38:16, tonyg wrote:
> > This makes sense, but can't you define issues a little better in the CL
> > description? Is this the reason I had to roll back that ephemeral port
change
> > this morning?
> 
> Or maybe just associate it with a bug.
> 
> lgtm

Bug added with additional notes.

[ariblue, 2014-10-17 02:01:07]

The CQ bit was checked by ariblue@google.com

[commit-bot: I haz the power, 2014-10-17 02:02:21]

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

[commit-bot: I haz the power, 2014-10-17 02:28:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-17 02:29:12]

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