From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P . Berrange" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: spurious error in check-dco job?
Date: Fri, 19 Mar 2021 11:44:24 +0100 [thread overview]
Message-ID: <fe4d7204-610c-37f2-b928-6a833dcf1e5f@redhat.com> (raw)
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
next reply other threads:[~2021-03-19 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 10:44 Philippe Mathieu-Daudé [this message]
2021-03-22 10:15 ` spurious error in check-dco job? Philippe Mathieu-Daudé
2021-03-22 10:54 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe4d7204-610c-37f2-b928-6a833dcf1e5f@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).