Re-enabling 720p WebRTC video quality test.

chrome/browser/media/chrome_webrtc_video_quality_browsertest.cc

 // Copyright 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "base/base64.h"
 #include "base/command_line.h"
 #include "base/environment.h"
 #include "base/files/file.h"
 #include "base/files/file_util.h"
 #include "base/files/scoped_temp_dir.h"
@@ skipping 50 matching lines @@
 static const struct VideoQualityTestConfig {
   const char* test_name;
   int width;
   int height;
   const base::FilePath::CharType* reference_video;
   const char* constraints;
 } kVideoConfigurations[] = {
   { "360p", 640, 360,
     test::kReferenceFileName360p,
     WebRtcTestBase::kAudioVideoCallConstraints360p },
-    // TODO(phoglund): Temporarily disabled on Windows because 720p has become
-    // very, very slow on Windows (550s).
-    // See https://code.google.com/p/webrtc/issues/detail?id=4986.
-#if !defined(OS_WIN)
     { "720p", 1280, 720,
     test::kReferenceFileName720p,
     WebRtcTestBase::kAudioVideoCallConstraints720p },
-#endif
 };
 
 // Test the video quality of the WebRTC output.
 //
 // Prerequisites: This test case must run on a machine with a chrome playing
 // the video from the reference files located in GetReferenceFilesDir().
 // The file kReferenceY4mFileName.kY4mFileExtension is played using a
 // FileVideoCaptureDevice and its sibling with kYuvFileExtension is used for
 // comparison.
 //
@@ skipping 241 matching lines @@
 
   // Poll slower here to avoid flooding the log with messages: capturing and
   // sending frames take quite a bit of time.
   int polling_interval_msec = 1000;
 
   EXPECT_TRUE(test::PollingWaitUntil(
       "doneFrameCapturing()", "done-capturing", right_tab,
       polling_interval_msec));
 
   HangUp(left_tab);
+  CloseLastLocalStream(left_tab);
+  CloseLastLocalStream(right_tab);
 
   WriteCapturedFramesToWorkingDir(right_tab);
 
   // Shut everything down to avoid having the javascript race with the analysis
   // tools. For instance, dont have console log printouts interleave with the
   // RESULT lines from the analysis tools (crbug.com/323200).
   chrome::CloseWebContents(browser(), left_tab, false);
   chrome::CloseWebContents(browser(), right_tab, false);
 
   ASSERT_TRUE(RunARGBtoI420Converter(
       test_config_.width, test_config_.height,
       GetWorkingDir().Append(kCapturedYuvFileName)));
   ASSERT_TRUE(CompareVideosAndPrintResult(
       test_config_.test_name,
       test_config_.width,
       test_config_.height,
       GetWorkingDir().Append(kCapturedYuvFileName),
       test::GetReferenceFilesDir()
           .Append(test_config_.reference_video)
           .AddExtension(test::kYuvFileExtension),
       GetWorkingDir().Append(kStatsFileName)));
 }