DriveFileSystemExtensionApiTest.FileSystemOperations flaky on Linux Chromium OS ASan LSan Tests (1) |
|||||||||||||
Issue descriptionbrowser_tests flaky on chromium.memory/Linux Chromium OS ASan LSan Tests (1) Type: build-failure Builders failed on: - Linux Chromium OS ASan LSan Tests (1): https://build.chromium.org/p/chromium.memory/builders/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29
,
Jan 12 2017
Assigning this to one of the owners in //src/chrome/browser/chromeos/file_manager/ where the flaky test comes from. fukino@: Could you please assign it to someone who's related to this flaky test?
,
Jan 12 2017
,
Feb 23 2018
,
Feb 28 2018
,
Feb 28 2018
,
Feb 28 2018
,
Feb 28 2018
,
Feb 28 2018
,
Feb 28 2018
,
Mar 15 2018
Disabled in memory tests, shows some flakiness in release build: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=DriveFileSystemExtensionApiTest.FileSystemOperations
,
Apr 12 2018
,
Apr 12 2018
Looking at Linux Chromium OS ASan LSan Tests (1) https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=DriveFileSystemExtensionApiTest.FileSystemOperations All gray boxes. Does this mean flakey? No, not necessarily. Many of the builds are green if you click the gray boxes. Trick is to click gray boxes until you find one with a browser_test failure, and open its stdout link and search for the test name. Did this for first 20 gray boxes, and didn't I find any references to test DriveFileSystemExtensionApiTest.FileSystemOperations at all. If it is still flaking, it's not showing itself enough in current builds to be a concern WONTFIX (compared to our other flakey tests, which happen on pretty much every ever run). MUSTFIX. Sad that #1 didn't save the initial bot report in this bug. No data now, since they are not permalinks. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by xlai@chromium.org
, Jan 12 2017