Rerun the flaky test at the build in which it is just added or re-enabled. |
|
Issue descriptionhttps://findit-for-me.appspot.com/waterfall/check-flake?master_name=chromium.win&builder_name=Win7%20Tests%20(dbg)(1)&build_number=54848&step_name=ash_unittests%20on%20Windows-7-SP1&test_name=ToastManagerTest.NullMessageHasNoDismissButton In this case, the test was newly added at build 54809 (culprit is https://codereview.chromium.org/2506583005/), but somehow findit got it wrong at 54817. If we could get a different data point at build 54809, the result might be different. |
|
►
Sign in to add a comment |
|
Comment 1 by st...@chromium.org
, Apr 24 2017Owner: chanli@chromium.org
Status: Fixed (was: Available)