Disable BrowserTestWithProfileShortcutManager.WindowProperties for flakiness.

chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc

Index: chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc
diff --git a/chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc b/chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc
index 3d976ce0ecb6a73ed61207a0c075462a9718df79..41cbd3c3b1d3e4318e63908bd8dea5c5464424df 100644
--- a/chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc
+++ b/chrome/browser/ui/views/frame/browser_window_property_manager_browsertest_win.cc
@@ -100,9 +100,10 @@ class BrowserTestWithProfileShortcutManager : public InProcessBrowserTest {
   DISALLOW_COPY_AND_ASSIGN(BrowserTestWithProfileShortcutManager);
 };
 
+// Test is flaky on Win7 bots. See crbug.com/332628.
 // Check that the window properties on Windows are properly set.
 IN_PROC_BROWSER_TEST_F(BrowserTestWithProfileShortcutManager,
-                       WindowProperties) {
+                       DISABLED_WindowProperties) {
 #if defined(USE_ASH)
   // Disable this test in Metro+Ash where Windows window properties aren't used.
   if (CommandLine::ForCurrentProcess()->HasSwitch(switches::kAshBrowserTests))