Enable renegotiate tests.

Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
Committed: https://crrev.com/f62387805b09fbee97a64d207ddc7ee8d3c7e085
Cr-Commit-Position: refs/heads/master@{#407146}

[ehmaldonado_chromium, 2016-07-22 11:48:21]

These tests run fine on my machine.

[ehmaldonado_chromium, 2016-07-22 11:48:35]

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

[ehmaldonado_chromium, 2016-07-22 11:54:31]

Description was changed from

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

It might have been fixed by now.

BUG=484826
==========

to

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
==========

[ehmaldonado_chromium, 2016-07-22 11:54:32]

Description was changed from

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

It might have been fixed by now.

BUG=484826
==========

to

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
==========

[phoglund_chromium, 2016-07-22 11:57:30]

lgtm, but note the bug claimed they were flaky so you need to keep an eye on
these tests for a few days and turn them back off again if the fail flakily.

[ehmaldonado_chromium, 2016-07-22 13:04:25]

The CQ bit was checked by ehmaldonado@chromium.org

[commit-bot: I haz the power, 2016-07-22 13:04:37]

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

[ehmaldonado_chromium, 2016-07-22 13:04:49]

On 2016/07/22 11:57:30, phoglund_chrome wrote:
> lgtm, but note the bug claimed they were flaky so you need to keep an eye on
> these tests for a few days and turn them back off again if the fail flakily.

A fail would reflect in the waterfall, or how should I keep track of it?

[ehmaldonado_chromium, 2016-07-22 13:04:52]

On 2016/07/22 11:57:30, phoglund_chrome wrote:
> lgtm, but note the bug claimed they were flaky so you need to keep an eye on
> these tests for a few days and turn them back off again if the fail flakily.

A fail would reflect in the waterfall, or how should I keep track of it?

[commit-bot: I haz the power, 2016-07-22 13:43:40]

Description was changed from

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
==========

to

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
==========

[commit-bot: I haz the power, 2016-07-22 13:43:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-22 13:45:58]

Description was changed from

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826
==========

to

==========
Enable renegotiate tests.

The tests CanMakeAudioCallAndThenRenegotiateToVideo and
CanMakeVideoCallAndThenRenegotiateToAudio had been disabled because of a
bug in libjingle/webrtc.

These tests run fine in my machine. It might have been
fixed by now.

BUG=484826

Committed: https://crrev.com/f62387805b09fbee97a64d207ddc7ee8d3c7e085
Cr-Commit-Position: refs/heads/master@{#407146}
==========

[commit-bot: I haz the power, 2016-07-22 13:45:59]

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

[phoglund_chromium, 2016-07-22 13:51:10]

On 2016/07/22 13:04:52, ehmaldonado_chromium wrote:
> On 2016/07/22 11:57:30, phoglund_chrome wrote:
> > lgtm, but note the bug claimed they were flaky so you need to keep an eye on
> > these tests for a few days and turn them back off again if the fail flakily.
> 
> A fail would reflect in the waterfall, or how should I keep track of it?

Yes. On, say, Monday, go through the build history for a few WebRTC Chromium
bots. If you see content_browsertests failures every now and then, check the
logs. If this test is in there its still flaky.