Viz Windows Flaky Timeouts |
|||
Issue descriptionA series of viz_browser_tests have been flaking on Windows, especially 10 x64. Each failure is just a timeout with no listed error or stack trace. 5 suites are consistently failing: - ManifestVerifierBrowserTest.* - PrefHashBrowserTest* - UserInitiatedRunsDisabled* - UserInitiatedRunsEnabled* - WithVaryingSeeds/ChromeCleanerPromptUserTest.* Some other tests have also shown occasional flakes: - BluetoothApiTest.Discovery - ChromeOriginTrialsDisabledFeaturesTest.DisabledFeaturesSetOnCommandLine/1 - ChromeTracingDelegateBrowserTestOnStartup.ScenarioSetFromFieldtrial - ChromeTracingDelegateBrowserTestOnStartup.StartupTracingThrottle - ExtensionApiTabTest.UpdateWindowResize - FirstRunBrowserTest.SetShouldShowWelcomePage - FullscreenControllerTest.FastMouseLockUnlockRelock - PictureInPictureWindowControllerBrowserTest.CreationAndVisibility - ProfileChooserViewExtensionsTest.InvokeUi_Guest - ProfileMainNetworkContext/NetworkContextConfigurationBrowserTest.FileURL/0 - PolicyTest.TaskManagerEndProcessEnabled - StartupBrowserCreatorTest.ProfilesLaunchedAfterCrash
,
Apr 3 2018
Issue 827813 has been merged into this issue.
,
Apr 3 2018
Issue 827843 has been merged into this issue.
,
Apr 3 2018
Issue 827309 has been merged into this issue.
,
Apr 3 2018
Issue 827308 has been merged into this issue.
,
Apr 3 2018
Filter updated to include those new flakes
,
Apr 4 2018
Found some more flakes: https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/137070 AllowLocalhostErrorsSSLHostStateDelegateTest.LocalhostErrorWithFlag V4SafeBrowsingServiceTest.CheckBrowseUrl ExtensionInstallDialogViewInteractiveBrowserTest.InvokeUi_External
,
Apr 4 2018
Those are a teardown on an incorrect thread in third_party/preferences code. It's different from the timeout flakes that we've seen Viz cause. I've filed issue 829112 to track those separately.
,
Apr 5 2018
,
Apr 5 2018
A lot more viz_browser_tests failures are being seen now. They aren't timeouts but rather test failures. Please see Issue 829300 . It is affecting the CQ so it's marked P1.
,
May 15 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/363e22e8984141f9dc36c6fd7a80c8218f60af20 commit 363e22e8984141f9dc36c6fd7a80c8218f60af20 Author: jonross <jonross@chromium.org> Date: Tue May 15 22:47:08 2018 Re-enable flaky viz_browser_tests A while back there were a series of viz_browser_tests that were timing out on Windows trybots. There was no stack traces at the time. We could no reproduce these locally. However there were a bunch of other timeouts happening on Windows outside of viz configurations at the time. This speculatively re-enables those tests. viz_browser_tests is not currently on Windows CQ so Windows related failures will only affect our FYI bots. TBR=kylechar@chromium.org TEST=viz_browser_tests Bug: 821029 Change-Id: I8a1d3369915da11e0110c9bf9611d0130fb8f470 Reviewed-on: https://chromium-review.googlesource.com/1060417 Reviewed-by: Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#558867} [modify] https://crrev.com/363e22e8984141f9dc36c6fd7a80c8218f60af20/testing/buildbot/filters/viz.browser_tests.filter
,
Jun 6 2018
These have become stable. |
|||
►
Sign in to add a comment |
|||
Comment 1 by zmin@chromium.org
, Apr 3 2018