Re: Cirrus-CI all red

[Daniel P . Berrangé]

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 :|