[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: spurious error in check-dco job?
|
From: |
Philippe Mathieu-Daudé |
|
Subject: |
Re: spurious error in check-dco job? |
|
Date: |
Mon, 22 Mar 2021 11:15:44 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 |
+Wainer
On 3/19/21 11:44 AM, 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
Can this be a runner capabilities problem? Sorry but
I'm lost here.