MasterSlaveLKGMSync failed on 3 devices in nyc-android-pfq |
|||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromeos/bob-nyc-android-pfq/517 https://luci-milo.appspot.com/buildbot/chromeos/caroline-nyc-android-pfq/947 https://luci-milo.appspot.com/buildbot/chromeos/hana-nyc-android-pfq/517 > remote: Short term bandwidth rate limit exceeded for 3su6n15k.default@developer.gserviceaccount.com This looks like the cause. 22:17:27: INFO: RunCommand: git clone https://chrome-internal.googlesource.com/chromeos/manifest-versions /b/c/cbuild/repository/manifest-versions-internal in /b/c/cbuild/repository/manifest-versions-internal 22:17:31: WARNING: git reported transient error (cmd=clone https://chrome-internal.googlesource.com/chromeos/manifest-versions /b/c/cbuild/repository/manifest-versions-internal); retrying Traceback (most recent call last): File "/b/c/cbuild/repository/chromite/lib/retry_util.py", line 176, in _Wrapper ret = func(*args, **kwargs) File "/b/c/cbuild/repository/chromite/lib/retry_util.py", line 242, in _run return functor(*args, **kwargs) File "/b/c/cbuild/repository/chromite/lib/cros_build_lib.py", line 653, in RunCommand raise RunCommandError(msg, cmd_result) RunCommandError: return code: 128; command: git clone https://chrome-internal.googlesource.com/chromeos/manifest-versions /b/c/cbuild/repository/manifest-versions-internal Cloning into '/b/c/cbuild/repository/manifest-versions-internal'... remote: Short term bandwidth rate limit exceeded for 3su6n15k.default@developer.gserviceaccount.com fatal: protocol error: bad pack header [W git.go:283] Transient error string identified in STDERR: "fatal: protocol error: bad pack header\n" [W git.go:294] Retrying after 3s (rc=128): transient error string encountered Cloning into '/b/c/cbuild/repository/manifest-versions-internal'... fatal: Unable to read current working directory: No such file or directory [W git.go:317] Command completed with rc 128 after 1 transient failure(s).
,
Sep 8 2017
There've been recent changes relating to LKGMSync, including (I see) a failure in the Chrome PFQ within the past 12 hours or so. stevenjb@ - is there anything new in this bug?
,
Sep 8 2017
I note that the current nyc-android-pfq builders all seem to have gotten cleanly through the problem phase in the most recent build.
,
Sep 12 2017
Problem hasn't recurred, so I'm declaring this a one-time glitch. |
|||
►
Sign in to add a comment |
|||
Comment 1 by yamaguchi@chromium.org
, Sep 8 2017Status: Untriaged (was: Available)