"commit-git-patch" step in run_presubmit should not cause build failure |
||||||
Issue description"commit-git-patch" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyGwsSBUZsYWtlIhBjb21taXQtZ2l0LXBhdGNoDA. This flaky test/step was previously tracked in issue 679863 .
,
Feb 1 2017
,
Feb 2 2017
,
Feb 8 2017
,
Apr 18 2017
Detected 4 new flakes for test/step "commit-git-patch". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyGwsSBUZsYWtlIhBjb21taXQtZ2l0LXBhdGNoDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).
,
Apr 19 2017
Um, if there's nothing to commit, then this should be treated as a patch failure right? It basically means that the CL in question was already committed.
,
Apr 21 2017
I think #6 is correct, look at the last comment on the issues that caused this to fire: https://codereview.chromium.org/2825683002 and https://codereview.chromium.org/2821563002 Looks like it's WAI? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hinoka@chromium.org
, Feb 1 2017