On Tue, Nov 09, 2021 at 11:27:42AM +0000, Alex Bennée wrote: > > Daniel P. Berrangé <berra...@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 :|
