"[trigger] chrome_public_test_apk" is flaky |
|||
Issue description"[trigger]" 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 infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyFAsSBUZsYWtlIglbdHJpZ2dlcl0M.
,
Feb 24 2017
Some problem with the recipe scripts? Over to Infra for further analysis/triage.
,
Feb 24 2017
It looks like what happened is the test failed, and had 1736 tests failed. It then tried to re-trigger without patch, and it tried to pass all those test names on the command line, which hit some argument list length limit. Not a trooper issue, but this should probably be fixed. cc-ing people.
,
Feb 24 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by treib@chromium.org
, Feb 24 2017Summary: "[trigger] chrome_public_test_apk" is flaky (was: "[trigger]" is flaky)