[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cirrus-CI all red

From: Thomas Huth
Subject: Re: Cirrus-CI all red
Date: Tue, 16 Nov 2021 10:15:18 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0

On 09/11/2021 12.32, Daniel P. Berrangé wrote:
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):

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

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.

We should maybe also simply bump the timeout for the cirrus jobs ... sometimes they get delayed and just need a little bit more than 60 minutes to finish ... so would it be OK to us 70 or 80 minutes here?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]