WebRTC: Re-enable 30s datachannel telemetry test.

WebRTC: Re-enable 30s datachannel telemetry test.

BUG=chromium:726811
Review-Url: https://codereview.chromium.org/2908383002
Cr-Commit-Position: refs/heads/master@{#475797}
Committed: https://chromium.googlesource.com/chromium/src/+/0e5657e03379575203b9617d955e1c410d3db7f2

[ehmaldonado_chromium, 2017-05-30 14:02:58]

ehmaldonado@chromium.org changed reviewers:
+ charliea@chromium.org, nednguyen@google.com

[ehmaldonado_chromium, 2017-05-30 14:02:59]

PTAL.
multiple_peerconnections is no longer failing.

[ehmaldonado_chromium, 2017-05-30 14:03:18]

On 2017/05/30 14:02:59, ehmaldonado_chromium wrote:
> PTAL.
> multiple_peerconnections is no longer failing.

Should I add NOTRY=True?

[nednguyen, 2017-05-30 14:04:53]

lgtm

On 2017/05/30 14:03:18, ehmaldonado_chromium wrote:
> On 2017/05/30 14:02:59, ehmaldonado_chromium wrote:
> > PTAL.
> > multiple_peerconnections is no longer failing.
> 
> Should I add NOTRY=True?
No, because this may be smoke tested on CQ, so there is a risk that we slip in a
CQ breaking test.

[charliea (OOO until 10-5), 2017-05-30 16:02:48]

lgtm

[ehmaldonado_chromium, 2017-05-31 03:01:58]

The CQ bit was checked by ehmaldonado@chromium.org

[commit-bot: I haz the power, 2017-05-31 03:02:21]

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-05-31 04:23:55]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1496199718845360, "parent_rev":
"e1f7b2223d6390b8b25836c33a7762ce6bc15fa0", "commit_rev":
"0e5657e03379575203b9617d955e1c410d3db7f2"}

[commit-bot: I haz the power, 2017-05-31 04:24:05]

Description was changed from

==========
WebRTC: Re-enable 30s datachannel telemetry test.

BUG=chromium:726811
==========

to

==========
WebRTC: Re-enable 30s datachannel telemetry test.

BUG=chromium:726811

Review-Url: https://codereview.chromium.org/2908383002
Cr-Commit-Position: refs/heads/master@{#475797}
Committed:
https://chromium.googlesource.com/chromium/src/+/0e5657e03379575203b9617d955e...
==========

[commit-bot: I haz the power, 2017-05-31 04:24:06]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/0e5657e03379575203b9617d955e...

[mikecase (-- gone --), 2017-06-06 22:48:44]

mikecase@chromium.org changed reviewers:
+ mikecase@chromium.org

[mikecase (-- gone --), 2017-06-06 22:48:45]

This test seems to be timing out on many of the desktop perf bots causing them
to fail.

Going to revert this CL

[mikecase (-- gone --), 2017-06-06 22:49:43]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2927673002/ by mikecase@chromium.org.

The reason for reverting is: Test timing out on many of the Desktop perf bots
such as...

Linux Perf
Mac 10.11 Perf.Mac Pro 10.11Perf
Win 7 Interl GPU Perf

and about 10 more..