"analyze report" is flaky |
||
Issue description"analyze" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers label. We have detected 7 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEgsSBUZsYWtlIgdhbmFseXplDA. This flaky test/step was previously tracked in issue 647885 .
,
Oct 7 2016
This was not a flake, but a reliable failure introduced here http://crrev.com/2397593003 and fixed here http://crrev.com/2403473002 . I suppose it was reported as "flake" only because it got fixed and passed on retry.
,
Oct 9 2016
We have more false positives :(. See issue 583446. The name is always trimmed to the first word to get rid of all random suffixes. We are working on a better solution, but for the moment that's the only reliable way to avoid having 100s of bugs filed for a single failing test suite. |
||
►
Sign in to add a comment |
||
Comment 1 by dpranke@chromium.org
, Oct 7 2016Summary: "analyze report" is flaky (was: "analyze" is flaky)