Flaky failures in mash_browser_tests (without timeout) on ChromeOS Ozone bots |
||
Issue descriptionSplitting this issue out from Latest builds for continuous builder: https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Ozone%20Tests%20%281%29?numbuilds=200 Latest builds for try bot: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng?numbuilds=200 Flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=mash_browser_tests Flakiness dashboard now shows that ExperimentalAppWindowApiTest.SetIcon CreateNewFolder/FileManagerBrowserTest.Test/{0,1,2,3} have become flaky. kmarshall@, quick question: Do changes for Fuchsia affect "ChromeOS Ozone"? (There were a couple of changes around the time that these tests became flaky.)
,
Jul 17 2017
This appears to be fixed now, looking at the latest builds. |
||
►
Sign in to add a comment |
||
Comment 1 by qyears...@chromium.org
, Jul 14 2017