From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Ed Maste" <emaste@freebsd.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
luoyonggang@gmail.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [RFC PATCH] .cirrus.yml: bump timeout period for MacOS builds
Date: Tue, 15 Dec 2020 09:56:27 +0000 [thread overview]
Message-ID: <20201215095627.GD121272@redhat.com> (raw)
In-Reply-To: <caaa48db-95b4-0765-2b96-e7f7298457fb@redhat.com>
On Mon, Dec 14, 2020 at 10:33:09AM +0100, Thomas Huth wrote:
> On 14/12/2020 10.24, Alex Bennée wrote:
> >
> > 罗勇刚(Yonggang Luo) <luoyonggang@gmail.com> writes:
> >
> >> On Mon, Dec 14, 2020 at 2:36 AM Philippe Mathieu-Daudé <f4bug@amsat.org>
> >> wrote:
> >>>
> >>> 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
> >>>
> >> Even two hour doesn't working, don't know why
> >
> > It seems to have jumped up quite considerably over a short period which
> > makes me think the underlying cause is something is getting stuck on
> > MacOS. Unfortunately it's hard to debug with just the logs because
> > whatever is taking the time might not be the last thing in the logs.
> >
> > Having a time-per-test metric would be useful here.
>
> Didn't Daniel post such a patch some weeks ago?
I posted a nasty hack for it, but Paolo has integrated nice support for
it into Meson git master
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 :|
prev parent reply other threads:[~2020-12-15 9:58 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é
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é [this message]
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=20201215095627.GD121272@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=f4bug@amsat.org \
--cc=luoyonggang@gmail.com \
--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).