From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Ed Maste" <emaste@freebsd.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [RFC PATCH] .cirrus.yml: bump timeout period for MacOS builds
Date: Sun, 13 Dec 2020 19:35:22 +0100 [thread overview]
Message-ID: <CAAdtpL6E1wbT_qrzARjR8M2b1s=jpVuT0y5iTA5wxh+559DQQA@mail.gmail.com> (raw)
In-Reply-To: <44c6c5c4-2152-b31f-9610-1a8e7f72037e@redhat.com>
On Wed, Nov 18, 2020 at 4:11 PM Thomas Huth <thuth@redhat.com> wrote:
> On 18/11/2020 15.07, Alex Bennée wrote:
> > These seem to trigger timeouts with some regularity.
> >
> > Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> > ---
> > .cirrus.yml | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/.cirrus.yml b/.cirrus.yml
> > index f0209b7a3e..08db7c419f 100644
> > --- a/.cirrus.yml
> > +++ b/.cirrus.yml
> > @@ -18,6 +18,7 @@ freebsd_12_task:
> > - gmake -j$(sysctl -n hw.ncpu) check V=1
> >
> > macos_task:
> > + timeout_in: 90m
> > osx_instance:
> > image: catalina-base
> > install_script:
> > @@ -32,6 +33,7 @@ macos_task:
> > - gmake check V=1
> >
> > macos_xcode_task:
> > + timeout_in: 90m
> > osx_instance:
> > # this is an alias for the latest Xcode
> > image: catalina-xcode
> >
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
> ... we could maybe also split the --target-list between the two jobs if they
> take too long...
Maybe it's time, 90min reached:
https://cirrus-ci.com/task/5774549872541696
next prev parent reply other threads:[~2020-12-13 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:07 [RFC PATCH] .cirrus.yml: bump timeout period for MacOS builds Alex Bennée
2020-11-18 15:11 ` Thomas Huth
2020-12-13 18:35 ` Philippe Mathieu-Daudé [this message]
2020-12-13 19:18 ` 罗勇刚(Yonggang Luo)
2020-12-14 9:24 ` Alex Bennée
2020-12-14 9:33 ` Thomas Huth
2020-12-15 9:56 ` 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='CAAdtpL6E1wbT_qrzARjR8M2b1s=jpVuT0y5iTA5wxh+559DQQA@mail.gmail.com' \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=pbonzini@redhat.com \
--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 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).