bot_update fails flakily with Could Not Find c:\b\build\slave\cache_dir\chromium.googlesource.com-external-snappy.lock |
|||||
Issue descriptionIn crbug.com/629643 we see a bot_update failure during gclient sync with the following message: Could Not Find c:\b\build\slave\cache_dir\chromium.googlesource.com-external-snappy.lock It's not clear to me what the root cause of this failure is, but I wonder if bot_update should be retrying the sync in this case, or if there's a bug that can be fixed higher in the stack.
,
Jul 25 2016
As decided in issue 630900, please do not use Infra>Flakiness label for specific flaky tests or infra flakes and instead assign issues to specific component that is flaky.
,
Jul 25 2016
,
Jul 25 2016
hinoka, any ideas?
,
Jul 25 2016
This is the build in reference: https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6716 I don't see any bot_update failures? For context, the lock messages are vestiges of unused code. They look alarming but they don't actually mean anything. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by seanmccullough@google.com
, Jul 21 2016