Sample failed build due to flakiness: https://ci.chromium.org/buildbot/chromium.mac/Mac10.13%20Tests%20%28dbg%29/5245 Culprit (70.0% confidence): https://chromium-review.googlesource.com/q/I649f105c58d9643dd4cab5aa685b3c6e4556097e Analysis: https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVyzQELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKWAWNocm9taXVtLm1hYy9NYWMxMC4xMyBUZXN0cyAoZGJnKS81MjQ1L2Jyb3dzZXJfdGVzdHMgb24gKG5vbmUpIEdQVSBvbiBNYWMvUVc1a2NtOXBaRlZ6WWtOdmRXNTBWR1Z6ZEM1VVpYTjBUbTlOZFd4MGFYQnNaVU5oYkd4elVtVnRiM1psU1c1RFlXeHNZbUZqYXc9PQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM Please revert the culprit, or disable the test and find the appropriate owner. If the culprit above is wrong, please file a bug using this link: https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Analyzer%20-%20Wrong%20result%20for%20AndroidUsbCountTest.TestNoMultipleCallsRemoveInCallback&comment=Link%20to%20Analysis%3A%20https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVyzQELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKWAWNocm9taXVtLm1hYy9NYWMxMC4xMyBUZXN0cyAoZGJnKS81MjQ1L2Jyb3dzZXJfdGVzdHMgb24gKG5vbmUpIEdQVSBvbiBNYWMvUVc1a2NtOXBaRlZ6WWtOdmRXNTBWR1Z6ZEM1VVpYTjBUbTlOZFd4MGFYQnNaVU5oYkd4elVtVnRiM1psU1c1RFlXeHNZbUZqYXc9PQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e3170c4fc248af87dee30af2acc06767d1e3a936 commit e3170c4fc248af87dee30af2acc06767d1e3a936 Author: Oskar Sundbom <ossu@chromium.org> Date: Thu Sep 13 13:40:11 2018 Disable AndroidUsbCountTest.TestNoMultipleCallsRemoveAddInCallback It's been flaky for a long time. Bug: 883680 Tbr: pfeldman@chromium.org Change-Id: Id9d37b76480dab89325d2d454f921bb76288fb4d Reviewed-on: https://chromium-review.googlesource.com/1224551 Reviewed-by: Oskar Sundbom <ossu@chromium.org> Commit-Queue: Oskar Sundbom <ossu@chromium.org> Cr-Commit-Position: refs/heads/master@{#590991} [modify] https://crrev.com/e3170c4fc248af87dee30af2acc06767d1e3a936/chrome/browser/devtools/device/usb/android_usb_browsertest.cc
Not working on DevTools anymore. FWIW, any test that uses IsIdleForTesting is bound to be flaky to some extent.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2b4cda586f3e85c9c86b36aeebf07f8a984b3953 commit 2b4cda586f3e85c9c86b36aeebf07f8a984b3953 Author: Xiyuan Xia <xiyuan@chromium.org> Date: Wed Dec 12 17:24:05 2018 Remove MessageLoopCurrent::IsIdleForTesting in AndroidUsbCountTest Testing of message loop idle seems not relevant to the tests and is bound to be flaky in browser_tests. Bug: 914380 , 883680 Change-Id: Iac6862c995ae105b8451f0cbcb544f64473c0d85 Reviewed-on: https://chromium-review.googlesource.com/c/1374199 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#615938} [modify] https://crrev.com/2b4cda586f3e85c9c86b36aeebf07f8a984b3953/chrome/browser/devtools/device/usb/android_usb_browsertest.cc
Comment 1 by ossu@chromium.org
, Sep 13Status: Assigned (was: Untriaged)