From 31fd45304980586150e015e9c78639dcac81700d Mon Sep 17 00:00:00 2001 From: "ccameron@chromium.org" Date: Tue, 29 Jan 2013 20:34:39 +0000 Subject: Don't use preserve-3d in GpuMemoryTest. Using preserve-3d hits an O(n^2) sort, which makes the test time-out on Windows debug builds. A Windows debug build now runs in about 3 seconds. TBR=ccameron BUG=171512 Review URL: https://codereview.chromium.org/12089055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@179403 0039d316-1c4b-4281-b951-d872f2087c98 --- content/browser/gpu/gpu_memory_test.cc | 4 ---- 1 file changed, 4 deletions(-) (limited to 'content/browser/gpu/gpu_memory_test.cc') diff --git a/content/browser/gpu/gpu_memory_test.cc b/content/browser/gpu/gpu_memory_test.cc index d8d8610..fc62846 100644 --- a/content/browser/gpu/gpu_memory_test.cc +++ b/content/browser/gpu/gpu_memory_test.cc @@ -235,10 +235,6 @@ IN_PROC_BROWSER_TEST_F(GpuMemoryTest, SingleWindowDoesNotExceedLimit) { if (!AllowTestsToRun()) return; - // crbug.com/171512, timeout on Win Debug. - if (GPUTestBotConfig::CurrentConfigMatches("WIN DEBUG")) - return; - content::Shell* tab = CreateNewTab(); LoadPage(tab, PAGE_CSS3D, kMemoryLimitMB); // Make sure that the CSS3D page maxes out a single tab's budget (otherwise -- cgit v1.1