"gclient (with 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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRnY2xpZW50ICh3aXRoIHBhdGNoKQw.
The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4.
This flaky test/step was previously tracked in issue 733870 .
Comment 1 by seanmccullough@chromium.org
, Jul 10 2017""" 18:17:47: WARNING: GS_ERROR: ServiceException: 503 None 18:17:47: ERROR: cros chrome-sdk failed before completing. """ """ ServiceException: 503 Service Unavailable. If you have recently changed https_validate_certificates from True to False in your boto configuration file, please delete any cached access tokens in your filesystem (at /home/chrome-bot/.gsutil/credstore) and try again """ Are the two error messages I see in the most recent builds. I ssh'd into slave187-c4 to check /home/chrome-bot/.gsutil/credstore and it doesn't mention https_validate_certificates at all AFAICT.