Remove TestMediaStreamVideoRenderer usage from LayoutTests.

Remove TestMediaStreamVideoRenderer usage from LayoutTests.

When running layout tests, there isn't a real video renderer for media streams
but a TestMediaStreamVideoRenderer implementation instead.

This implementation generates a stream of white frames
and sends them in certain intervals.

Video content aren't the real content and video events are also useless.

BUG=704302

[Yeol Park, 2017-03-30 02:15:10]

Description was changed from

==========
Remove TestMediaStreamVideoRenderer usage from LayoutTests.

When running layout tests, there isn't a real video renderer for media streams
but a TestMediaStreamVideoRenderer implementation instead.

This implementation generates a stream of white frames
and sends them in certain intervals.

Video content aren't the real content and video events are also useless.

BUG=704302
==========

to

==========
Remove TestMediaStreamVideoRenderer usage from LayoutTests.

When running layout tests, there isn't a real video renderer for media streams
but a TestMediaStreamVideoRenderer implementation instead.

This implementation generates a stream of white frames
and sends them in certain intervals.

Video content aren't the real content and video events are also useless.

BUG=704302
==========

[Yeol Park, 2017-03-30 02:15:10]

peary2@gmail.com changed reviewers:
+ emircan@chromium.org, mkwst@chromium.org, peter@chromium.org

[Yeol Park, 2017-03-30 02:15:32]

PTAL :)

[emircan, 2017-03-30 03:37:03]

The CQ bit was checked by emircan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-30 03:37:34]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-30 05:09:57]

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

[commit-bot: I haz the power, 2017-03-30 05:09:58]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Yeol Park, 2017-03-30 05:59:47]

The CQ bit was checked by peary2@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-03-30 06:00:09]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-30 06:00:10]

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

[commit-bot: I haz the power, 2017-03-30 06:00:11]

Dry run: No L-G-T-M from a valid reviewer yet.
CQ run can only be started once the patch has received an L-G-T-M from a full
committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,_not_ a
full super star committer.
Committers are members of the group "project-chromium-committers".
Note that this has nothing to do with OWNERS files.

[Mike West, 2017-03-30 06:31:34]

The failing layout tests suggest that we still need this. WDYT?

[emircan, 2017-03-30 17:08:25]

Thanks for your work on this Park. I only opened that bug to understand the
reasons behind this design decision and make a discussion. I am not sure if this
is something we need to change yet. Also, it would require more changes in tests
that rely on the previous behavior as we can see from the failing ones. 

Thanks again for your time, but I would recommend waiting on this. I will ping
the bug to see if there can be progress. In the meantime, I would recommend
looking at issues marked with Hotlist-GoodFirstBug.
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Hotlist%3DGoodFirstB...