No longer requiring pixel output for WebRTC tests.

No longer requiring pixel output for WebRTC tests.

We used to require pixel output for our canvas-scraping, but that
appears to no longer be required. This speeds up the test 3x on my
win machine, from 30 seconds to about 10.

The content_browsertests on ChromeOS will still enable pixel
output since it seems the requirements there are different - video
tags will not work unless that is enabled, it seems. I think
that's fine since our original problem was with the browser_tests
anyway, and I think the content_browsertests are probably fast
enough on ChromeOS anyway (whereas the browser_tests weren't).

BUG=396505
Committed: https://crrev.com/e6a342dcab57c3a2de1fd21301f37fdf3f8ad070
Cr-Commit-Position: refs/heads/master@{#297654}

[phoglund_chromium, 2014-09-29 12:22:22]

phoglund@chromium.org changed reviewers:
+ tommi@chromium.org

[phoglund_chromium, 2014-09-30 09:19:08]

phoglund@chromium.org changed reviewers:
+ vrk@chromium.org
- tommi@chromium.org

[phoglund_chromium, 2014-09-30 09:19:26]

tommi seems busy; vrk can you have a look?

[no longer working on chromium, 2014-09-30 15:29:11]

On 2014/09/30 09:19:26, phoglund wrote:
> tommi seems busy; vrk can you have a look?

lgtm

[phoglund_chromium, 2014-09-30 15:34:34]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-09-30 15:35:18]

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

[commit-bot: I haz the power, 2014-09-30 15:43:02]

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

[commit-bot: I haz the power, 2014-09-30 15:43:03]

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

[phoglund_chromium, 2014-09-30 15:45:04]

phoglund@chromium.org changed reviewers:
+ tommi@chromium.org, xians@google.com
- vrk@chromium.org

[phoglund_chromium, 2014-09-30 15:45:40]

Oh, I need a owner stamp from tommi anyway. Alright, let's do this tomorrow
instead then.

[tommi (sloooow) - chröme, 2014-09-30 18:08:20]

The CQ bit was checked by tommi@chromium.org

[tommi (sloooow) - chröme, 2014-09-30 18:08:21]

lgtm

[commit-bot: I haz the power, 2014-09-30 18:10:27]

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

[commit-bot: I haz the power, 2014-09-30 18:42:09]

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

[commit-bot: I haz the power, 2014-09-30 18:42:10]

Try jobs failed on following builders:
  android_dbg_tests_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tes...)

[phoglund_chromium, 2014-10-01 08:25:37]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-10-01 08:26:38]

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

[commit-bot: I haz the power, 2014-10-01 10:55:36]

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

[commit-bot: I haz the power, 2014-10-01 10:55:37]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[phoglund_chromium, 2014-10-01 11:32:11]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-10-01 11:32:50]

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

[phoglund_chromium, 2014-10-01 11:34:18]

The CQ bit was unchecked by phoglund@chromium.org

[phoglund_chromium, 2014-10-01 11:45:53]

The CQ bit was checked by phoglund@chromium.org

[phoglund_chromium, 2014-10-01 11:45:56]

The CQ bit was unchecked by phoglund@chromium.org

[phoglund_chromium, 2014-10-01 11:46:27]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-10-01 11:46:57]

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

[commit-bot: I haz the power, 2014-10-01 13:40:25]

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

[commit-bot: I haz the power, 2014-10-01 13:40:26]

Try jobs failed on following builders:
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[phoglund_chromium, 2014-10-01 14:01:21]

On 2014/10/01 13:40:26, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   win_chromium_x64_rel_swarming on tryserver.chromium.win
>
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

Oh that is interesting, if win_chromium_x64_rel_swarming happens to get
scheduled on vm773-m4 it works, but on vm772-m4, vm768-m4 or vm328-m4 it fails.
Well, that sucks. OK, I will drop the content_browsertests part and see if I can
get away with that.

[phoglund_chromium, 2014-10-01 14:08:48]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-10-01 14:09:42]

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

[commit-bot: I haz the power, 2014-10-01 16:41:55]

Committed patchset #4 (id:60001) as 132a77adde8d2969d465f0d3bdb30039afe166b8

[commit-bot: I haz the power, 2014-10-01 16:42:36]

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

[phoglund_chromium, 2014-10-02 10:57:54]

A revert of this CL (patchset #4 id:60001) has been created in
https://codereview.chromium.org/619003003/ by phoglund@chromium.org.

The reason for reverting is: Turns out this change makes video+canvas grabbing
produce junk; this is not good since our tests depend on that working.
Reverting..