Re-enable VP9 resize test.

webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc

Index: webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc
diff --git a/webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc b/webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc
index d9148d6b67a199d1f89d924993b9868221a2559b..b4c10cc29169aa27b335aa0d64be5a26f4d18c91 100644
--- a/webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc
+++ b/webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc
@@ -730,12 +730,11 @@ TEST_F(VideoProcessorIntegrationTest, ProcessNoLossDenoiserOnVP9) {
 // Run with no packet loss, at low bitrate.
 // spatial_resize is on, so expect one resize during the sequence,
 // resize happens on delta frame. Expect only one key frame (first frame).
-TEST_F(VideoProcessorIntegrationTest,
-       DISABLED_ProcessNoLossSpatialResizeFrameDropVP9) {
+TEST_F(VideoProcessorIntegrationTest, ProcessNoLossSpatialResizeFrameDropVP9) {
   config_.networking_config.packet_loss_probability = 0;
   // Bitrate and frame rate profile.
   RateProfile rate_profile;
-  SetRateProfilePars(&rate_profile, 0, 50, 30, 0);
+  SetRateProfilePars(&rate_profile, 0, 90, 30, 0);

[stefan-webrtc, 2015/10/22 09:44:14]

I don't fully understand this change. Could you explain why the target bitrate
changes from 50 to 90?

[marpan, 2015/10/23 15:57:10]

resize logic was changed to allow for 3/4 resizing first (before going down to
1/2 if things are still bad), so for this test at 50k, 2 resize actions occur. 

Either needed to increase bitrate and keep 1 resize action (and also keep same
expected RC metric values), or keep the bitrate=50k and change some expected
values in RC metrics(line 749). Went back to the latter change now (as in
patch#3).

   rate_profile.frame_index_rate_update[1] = kNbrFramesLong + 1;
   rate_profile.num_frames = kNbrFramesLong;
   // Codec/network settings.