From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Ed Maste" <emaste@freebsd.org>, "Li-Wen Hsu" <lwhsu@freebsd.org>,
"Yonggang Luo" <luoyonggang@gmail.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Cirrus-CI all red
Date: Tue, 9 Nov 2021 10:45:18 +0100 [thread overview]
Message-ID: <4e540821-9bc2-77b5-ad70-ebc5df53e039@redhat.com> (raw)
In-Reply-To: <701011ce-8bc1-9e93-82ed-a4d72c70b2da@redhat.com>
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.
> 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).
Thomas
next prev parent reply other threads:[~2021-11-09 9:47 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 [this message]
2021-11-09 9:56 ` Daniel P. Berrangé
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=4e540821-9bc2-77b5-ad70-ebc5df53e039@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=emaste@freebsd.org \
--cc=luoyonggang@gmail.com \
--cc=lwhsu@freebsd.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).