Flaky coverage assertion in "stdlib_test"? |
|||
Issue descriptionI just ran three consecutive dry runs on the same patch: https://codereview.chromium.org/2253943003/# The first two failed for coverage reasons: https://luci-milo.appspot.com/swarming/task/3123e9630c234e10/steps/presubmit/0/stdout https://luci-milo.appspot.com/swarming/task/3123e742e1529510/steps/presubmit/0/stdout The third succeeded. As far as I can tell, the CL in question should not have affected coverage, and definitely shouldn't have affected it to that extent. This is clearly flaky, and I think the first two runs were very incorrect.
,
Jun 21 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 26 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by estaab@chromium.org
, Jun 21 2017