Split regular and perf WebRTC browser tests, remove CPU test.

This splits the main browser test so the webrtc-internals perf test is
the only one to run with a reference file and moves the normal tests to
use the generating fake device (i.e. the spinning green ball). This is
fine since the main test doesn't care, whereas the perf test must have
a somewhat realistic video to give realistic encode/decode numbers.

The CPU test can be thrown away since we have telemetry tests for that
now.

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

[phoglund_chromium, 2014-05-20 12:43:40]

kjellander: main review
tommi: owner stamp

https://codereview.chromium.org/294053002/diff/60001/chrome/browser/media/chr...
File chrome/browser/media/chrome_webrtc_perf_browsertest.cc (right):

https://codereview.chromium.org/294053002/diff/60001/chrome/browser/media/chr...
chrome/browser/media/chrome_webrtc_perf_browsertest.cc:1: // Copyright 2014 The
Chromium Authors. All rights reserved.
This code pretty much moved straight out of chrome_webrtc_browsertest.cc

[kjellander_chromium, 2014-05-20 12:53:28]

I suggest doing all preparations in one CL so that "make tree closing" can be
done in a small CL, since it's likely to get reverted. WDYT?

[phoglund_chromium, 2014-05-20 12:56:08]

On 2014/05/20 12:53:28, kjellander wrote:
> I suggest doing all preparations in one CL so that "make tree closing" can be
> done in a small CL, since it's likely to get reverted. WDYT?

Ok, sure.

[phoglund_chromium, 2014-05-22 17:38:11]

On 2014/05/20 12:56:08, phoglund wrote:
> On 2014/05/20 12:53:28, kjellander wrote:
> > I suggest doing all preparations in one CL so that "make tree closing" can
be
> > done in a small CL, since it's likely to get reverted. WDYT?
> 
> Ok, sure.

It's done; PTAL.

[kjellander_chromium, 2014-05-22 18:45:58]

Please update the title and mention which tests you're going to make tree
closing in a follow-up CL.

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
File chrome/browser/media/chrome_webrtc_browsertest.cc (right):

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
chrome/browser/media/chrome_webrtc_browsertest.cc:53:
ASSERT_TRUE(test::HasReferenceFilesInCheckout());
This should also go away, right?

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
chrome/browser/media/chrome_webrtc_browsertest.cc:81:
ASSERT_TRUE(test::HasReferenceFilesInCheckout());
Same here...

[phoglund_chromium, 2014-05-23 07:55:42]

PTAL

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
File chrome/browser/media/chrome_webrtc_browsertest.cc (right):

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
chrome/browser/media/chrome_webrtc_browsertest.cc:53:
ASSERT_TRUE(test::HasReferenceFilesInCheckout());
On 2014/05/22 18:45:59, kjellander wrote:
> This should also go away, right?

Good catch, you're right.

https://codereview.chromium.org/294053002/diff/80001/chrome/browser/media/chr...
chrome/browser/media/chrome_webrtc_browsertest.cc:81:
ASSERT_TRUE(test::HasReferenceFilesInCheckout());
On 2014/05/22 18:45:59, kjellander wrote:
> Same here...

Done.

[kjellander_chromium, 2014-05-23 08:05:45]

lgtm!

[phoglund_chromium, 2014-05-23 08:51:29]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-05-23 08:52:50]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/phoglund@chromium.org/294053002/110001

[phoglund_chromium, 2014-05-23 09:25:15]

tommi: owner stamp?

[commit-bot: I haz the power, 2014-05-23 11:10:11]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-05-23 11:14:26]

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

[commit-bot: I haz the power, 2014-05-23 11:14:28]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[tommi (sloooow) - chröme, 2014-05-23 11:39:53]

rs lgtm

[phoglund_chromium, 2014-05-23 12:12:12]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-05-23 12:12:28]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/phoglund@chromium.org/294053002/110001

[commit-bot: I haz the power, 2014-05-23 13:42:47]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-05-23 17:52:26]

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

[commit-bot: I haz the power, 2014-05-23 17:52:26]

Try jobs failed on following builders:
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)

[phoglund_chromium, 2014-05-26 07:52:08]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-05-26 07:52:23]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/phoglund@chromium.org/294053002/110001

[commit-bot: I haz the power, 2014-05-26 15:49:11]

Change committed as 272828