From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: Yonggang Luo <luoyonggang@gmail.com>,
Ed Maste <emaste@freebsd.org>, Li-Wen Hsu <lwhsu@freebsd.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Cirrus-CI all red
Date: Tue, 16 Nov 2021 11:40:55 +0100 [thread overview]
Message-ID: <06f45f57-c034-7286-cb89-358272938e3b@redhat.com> (raw)
In-Reply-To: <938ec78f-1ca1-f3df-26be-790e53d9cc7e@redhat.com>
On 11/16/21 10:15, Thomas Huth wrote:
> 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:
[...]
>>> 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?
Sounds a good idea, this would be more useful that what we have now.
next prev parent reply other threads:[~2021-11-16 10:41 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é
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é [this message]
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=06f45f57-c034-7286-cb89-358272938e3b@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=emaste@freebsd.org \
--cc=luoyonggang@gmail.com \
--cc=lwhsu@freebsd.org \
--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.