Re: spurious error in check-dco job?

["Daniel P. Berrangé" <berrange@redhat.com>]

On Fri, Mar 19, 2021 at 11:44:24AM +0100, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
> 
> I'm getting this error sometimes in the check-dco job:
> 
> Using docker image
> sha256:96fcfc3ceb2d65689c2918c1c501c45b2bd815d82e7fb3381048c9f252e7b046
> for registry.gitlab.com/philmd/qemu2/qemu/centos8:latest with digest
> registry.gitlab.com/philmd/qemu2/qemu/centos8@sha256:798eb3e5aa50eb04d60cdf1bfd08bcff5b443e933dcfd902ebda01927e2f6eb0
> ...
> $ .gitlab-ci.d/check-dco.py
> Traceback (most recent call last):
>   File ".gitlab-ci.d/check-dco.py", line 25, in <module>
>     stderr=subprocess.DEVNULL)
>   File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call
>     raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['git', 'fetch', 'check-dco',
> 'master']' returned non-zero exit status 128.
> 
> https://gitlab.com/philmd/qemu2/-/jobs/1108482890

I expect a transient error in gitlab's servers. Even regular CI
jobs sometimes fail when pulling from git.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|