Added NiceMock for MockRtcEventLog in several unittests where we don't care about the event logging.

webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc

Index: webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc
diff --git a/webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc b/webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc
index f2a14ea9cfacbd3b404c95c4ccdd7d6a6c9f8740..3cb54b2045078bfb9e0bc4016d5b6d97b6976bd7 100644
--- a/webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc
+++ b/webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc
@@ -92,7 +92,7 @@ class BitrateControllerTest : public ::testing::Test {
   TestBitrateObserver bitrate_observer_;
   BitrateController* controller_;
   RtcpBandwidthObserver* bandwidth_observer_;
-  webrtc::MockRtcEventLog event_log_;
+  testing::NiceMock<webrtc::MockRtcEventLog> event_log_;

[stefan-webrtc, 2016/07/05 12:16:27]

Given this I think you may be able to remove some of the less interesting
EXPECT_CALL(event_log_, ...) lines below? Or does it make sense to keep all of
them?

[ivoc, 2016/07/05 12:25:27]

Good point, since the purpose of these tests is not really to test the event
log, I decided to just remove them all.

 };
 
 TEST_F(BitrateControllerTest, DefaultMinMaxBitrate) {