"gclient (with patch)" is flaky |
||||
Issue description"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 4 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 848040 .
,
Jun 28 2018
A majority of the flakes this week appear to be from chromeos-amd64-generic-rel failing on the cros chrome-sdk hook.
,
Jun 28 2018
It fails pretty quickly into the cros hook. A successful sync takes ~4 min: https://luci-milo.appspot.com/swarming/task/3e60fd60881d6510 It failed in just over 1 min: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromeos-amd64-generic-rel/34690 The failure has a pretty long gsutil stack trace: https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8942482314152970944%2F%2B%2Fsteps%2Fgclient_runhooks__with_patch_%2F0%2Fstdout Maybe GS flakiness? Not sure why we only see it in the cros hook. Let's wait to see if it keeps happening, and archive otherwise.
,
Jun 28 2018
SGTM. Will hold open through tomorrow.
,
Jun 29 2018
Detected 4 new flakes for test/step "gclient (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRnY2xpZW50ICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app.
,
Jun 29 2018
Seems like we're holding steady at 3-4 of these a day -- not terribly severe, but a high enough frequency to trigger try-flakes. Thoughts?
,
Jun 29 2018
We clobber the cros cache before every cros gclient hook: https://chromium.googlesource.com/chromium/src/+/c4ff8e3990189cee497960139a287012c5183241/DEPS#2124 That's to avoid unbound growth in disk usage. We could try turning that off, then subsequent runs would be a no-op and potentially avoid the gsutil flake. But the cache would start to increase in size over time... Let me think about this a bit more
,
Jun 30 2018
Detected 3 new flakes for test/step "gclient (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRnY2xpZW50ICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app.
,
Jul 16
Last cros-cache related hook failure was on 06-29. Temporary gsutil network/consistency flake? Closing this out. |
||||
►
Sign in to add a comment |
||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Jun 27 2018