[IndexedDB] Adding traces, perf tests
[chromium-blink-merge.git] / tools / valgrind / gtest_exclude / interactive_ui_tests.gtest.txt
blob6ae761f0a912dc41e7e5341d98f58f10ff7ff078
1 # These test fail due to mmap Valgrind failures, see http://crbug.com/66677
2 CollectedCookiesTest.DoubleDisplay
3 CollectedCookiesTest.NavigateAway
4 InfoBarsUITest.TestInfoBarsCloseOnNewTheme
5 FastShutdown.SlowTermination
6 MouseLeaveTest.TestOnMouseOut
7 NotificationsPermissionTest.TestNoUserGestureInfobar
8 NotificationsPermissionTest.TestUserGestureInfobar
10 # These test fail due to timeout or limited buildslave support;
11 # http://crbug.com/67301
12 BrowserFocusTest.InterstitialFocus
13 BrowserFocusTest.FindFocusTest
14 BrowserFocusTest.FocusTraversalOnInterstitial
16 # Don't run FLAKY or FAILS tests under Valgrind and TSan
17 # as they tend to generate too many reports, see http://crbug.com/67959
18 # NB: Can't use FAILS_/FLAKY_ as it will be turned into *.* by chrome_tests.py!
19 *.FLAKY*
20 *.FAILS*
22 # Fails under Valgrind, see http://crbug.com/68068
23 DevToolsSanityTest.TestPauseWhenScriptIsRunning
25 # These tests time out under Valgrind, see http://crbug.com/163880
26 BrowserFocusTest.FocusOnReload
27 CommandsApiTest.Basic
28 ExtensionApiTest.NotificationsHasPermissionManifest
29 ExtensionCrashRecoveryTest.ReloadTabsWithBackgroundPage
30 ExtensionCrashRecoveryTest.TwoExtensionsCrashBothAtOnce
31 ExtensionCrashRecoveryTest.TwoExtensionsCrashFirst
32 ExtensionCrashRecoveryTest.TwoExtensionsOneByOne
33 FullscreenControllerInteractiveTest.TestTabExitsMouseLockOnNavigation
34 OmniboxViewTest.Escape