VirtualTimeAndResourceErrorLoopTest.RunAsyncTest is Flaky |
||
Issue descriptionFindit has detected a flake at test VirtualTimeAndResourceErrorLoopTest.RunAsyncTest. Culprit (100.0% confidence): https://chromium-review.googlesource.com/q/I14e7d1abd5d4c4746656fce634a33cc126680b56 Regression range: https://crrev.com/0712d9513ba17d569d6f96b07c8f7d0abaa1796f..c0a5df03e192d414ee51eb738bd3600611a8cb18?pretty=fuller Analysis: https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVyswELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJ9Y2hyb21pdW0ud2luL1dpbiA3IFRlc3RzIHg2NCAoMSkvMzMzMzgvaGVhZGxlc3NfYnJvd3NlcnRlc3RzL1ZtbHlkSFZoYkZScGJXVkJibVJTWlhOdmRYSmpaVVZ5Y205eVRHOXZjRlJsYzNRdVVuVnVRWE41Ym1OVVpYTjAMCxITTWFzdGVyRmxha2VBbmFseXNpcxgBDA If this result was incorrect, apply the label Findit-Incorrect-Result, mark the bug as Untriaged and the component Tools>Test>Findit>Flakiness.
,
Jan 15 2018
Shouldn't we just disable the flaky test and assign this bug to the author of the blamed CL (which is the CL that introduced the test)?
,
Jan 15 2018
Already reverted on Friday: https://chromium-review.googlesource.com/865774 |
||
►
Sign in to add a comment |
||
Comment 1 by hayato@chromium.org
, Jan 15 2018