Commit f01a3977 authored by grt@chromium.org's avatar grt@chromium.org

Revert "Disabling ChromeFrame.Launch" (r124964)

It is my belief that http://crrev.com/126334 fixes the underlying cause and that http://crrev.com/126280 makes the tests a little more robust against it.

BUG=81479
TEST=chrome_frame_tests.exe covers it
TBR=robertshield@chromium.org

Review URL: https://chromiumcodereview.appspot.com/9699060

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126818 0039d316-1c4b-4281-b951-d872f2087c98
parent 8711d222
...@@ -8,10 +8,7 @@ ...@@ -8,10 +8,7 @@
const int kLongWaitTimeout = 25 * 1000; const int kLongWaitTimeout = 25 * 1000;
// Note that this test fails occasionally. Disabling it altogether (rather than TEST(ChromeFrame, Launch) {
// marking as flaky to see if the failure cascades down to the next test.
// http://crbug.com/81479
TEST(ChromeFrame, DISABLED_Launch) {
MessageLoopForUI loop; MessageLoopForUI loop;
AutomationMockLaunch mock_launch(&loop, kLongWaitTimeout); AutomationMockLaunch mock_launch(&loop, kLongWaitTimeout);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment