From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>, "Ed Maste" <emaste@freebsd.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Yonggang Luo" <luoyonggang@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: Cirrus-CI all red
Date: Tue, 9 Nov 2021 11:32:23 +0000 [thread overview]
Message-ID: <YYpcR/SBHNlqj5CV@redhat.com> (raw)
In-Reply-To: <87fss5k1lv.fsf@linaro.org>
On Tue, Nov 09, 2021 at 11:27:42AM +0000, Alex Bennée wrote:
>
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Tue, Nov 09, 2021 at 10:45:18AM +0100, Thomas Huth wrote:
> >> On 09/11/2021 10.39, Philippe Mathieu-Daudé wrote:
> >> > FYI, as of today, the latest merge history is red (last 10 days):
> >> > https://cirrus-ci.com/github/qemu/qemu
> >> >
> >> > If we want to keep using this, we should somehow plug it to
> >> > GitLab-CI (i.e. Travis-CI is run as an external job there) so
> >> > the project maintainer can notice job failures.
> >>
> >> Well, considering that all the cirrus-run based jobs are currently failing
> >> due to the non-working API token, that does not seem to work very well
> >> either.
> >
> > Who owns the API token ? For other projects, this was addressed a while
> > ago by refreshing the token. I would have tried this myself for QEMU
> > but I don't have privileges on the QEMU projects in github/gitlab.
>
> OK I've updated the token (after I figured out the path to it):
>
> - top right, Settings
> - scroll to bottom "Your GitHub Organizations"
> - click gear icon
> - scroll to API settings, click Generate New Token
>
> It seems to be triggering the builds now although GitLab still reports
> failures for some other reason now.
The cirrus-run image we're using is lockde to version 0.3.0. I'm
testing an update to version 0.5.0 which has various reliability
fixes, essentially around making it retry on transient errors.
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 :|
next prev parent reply other threads:[~2021-11-09 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 9:39 Cirrus-CI all red Philippe Mathieu-Daudé
2021-11-09 9:45 ` Thomas Huth
2021-11-09 9:56 ` Daniel P. Berrangé
2021-11-09 11:27 ` Alex Bennée
2021-11-09 11:32 ` Daniel P. Berrangé [this message]
2021-11-16 9:15 ` Thomas Huth
2021-11-16 10:40 ` Philippe Mathieu-Daudé
2021-11-16 11:30 ` 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=YYpcR/SBHNlqj5CV@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=luoyonggang@gmail.com \
--cc=lwhsu@freebsd.org \
--cc=philmd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.