change the log level of cipd ensure command to info

I suspect the reason of INFRA_FAILURE in https://crbug.com/1477933#c10
is that cipd is busy with downloading on the packages (it's also
possible that cipd is stucked on one or more packages) and since the
log-level is error, it won't ouptut anything until it completes.
However, from bot_update PoV, gclient is considered as a stale process
because it won't write anything to stdout in 20min so it decide to kill
the process. This CL fix the issue by changing the log-level to info
instead.

R=sokcevic

Bug: 1477933
Change-Id: I2fa05bcfe7f63debeda3371e755b5e7c6d011f12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/4844365
Reviewed-by: Josip Sokcevic <sokcevic@chromium.org>
Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
changes/65/4844365/3
Yiwei Zhang 2 years ago committed by LUCI CQ
parent bb67064617
commit 28116103e4

@ -1774,7 +1774,7 @@ class CipdRoot(object):
'cipd',
'ensure',
'-log-level',
'error',
'info',
'-root',
self.root_dir,
'-ensure-file',
@ -1817,7 +1817,7 @@ class CipdRoot(object):
'cipd',
'ensure-file-resolve',
'-log-level',
'error',
'info',
'-ensure-file',
ensure_file,
'-json-output',

Loading…
Cancel
Save