From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Ed Maste" <emaste@freebsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Yonggang Luo" <luoyonggang@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: Cirrus-CI all red
Date: Tue, 9 Nov 2021 09:56:49 +0000 [thread overview]
Message-ID: <YYpF4coXvnStffD5@redhat.com> (raw)
In-Reply-To: <4e540821-9bc2-77b5-ad70-ebc5df53e039@redhat.com>
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.
> > Alternatively the windows job could be passed to GitLab:
> > https://docs.gitlab.com/ee/ci/runners/runner_cloud/windows_runner_cloud.html
>
> See:
>
> https://lists.gnu.org/archive/html/qemu-devel/2021-07/msg02474.html
>
> ... the problem is again that the shared runners are only single-threaded,
> so it's incredibly slow, especially if you have to re-install MSYS2 each
> time. I once tried to improve the patch by caching the MSYS2 installation,
> but it did not work that well either... (but if somebody wants to continue
> my work, I can rebase and send it out again, just let me know).
Potentially this is something where we can make sure of the Azure credits
QEMU is getting, though it would require someone to figure out shared
runner integration and maintain it...
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 9:58 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é [this message]
2021-11-09 11:27 ` Alex Bennée
2021-11-09 11:32 ` Daniel P. Berrangé
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=YYpF4coXvnStffD5@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.