From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: peter.maydell@linaro.org, "Fam Zheng" <famz@redhat.com>,
qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PULL 1/1] .travis.yml: add --disable-linux-user for some jobs
Date: Tue, 13 Mar 2018 14:04:26 +0000 [thread overview]
Message-ID: <20180313140426.GY3048@redhat.com> (raw)
In-Reply-To: <87fu54rs35.fsf@linaro.org>
On Tue, Mar 13, 2018 at 02:02:54PM +0000, Alex Bennée wrote:
>
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Fri, Feb 09, 2018 at 02:15:14PM +0000, Alex Bennée wrote:
> >> The modules and co-routine builds are only really relevant to softmmu
> >> builds and regularly timeout on Travis. Let's disable linux-user
> >> builds here for more headroom.
> >>
> >> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> >> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
> >>
> >> diff --git a/.travis.yml b/.travis.yml
> >> index 01a57399b5..0dd5020552 100644
> >> --- a/.travis.yml
> >> +++ b/.travis.yml
> >> @@ -52,9 +52,9 @@ env:
> >> - CONFIG=""
> >> - CONFIG="--enable-debug --enable-debug-tcg --enable-trace-backends=log"
> >> - CONFIG="--disable-linux-aio --disable-cap-ng --disable-attr --disable-brlapi --disable-uuid --disable-libusb"
> >> - - CONFIG="--enable-modules"
> >> - - CONFIG="--with-coroutine=ucontext"
> >> - - CONFIG="--with-coroutine=sigaltstack"
> >> + - CONFIG="--enable-modules --disable-linux-user"
> >> + - CONFIG="--with-coroutine=ucontext --disable-linux-user"
> >> + - CONFIG="--with-coroutine=sigaltstack --disable-linux-user"
> >
> > Since this merged, the 4th, 5th & 6th jobs are now reliably completing in
> > time, but the 1st and 3rd jobs are hitting timeouts on the majority of
> > runs :-(
>
> Yeah it's certainly a problem as QEMU has grown. The original
> .travis.yml split things up across architecture lines but we removed
> that in favour of "feature" selection.
>
> > We've already got a lot of jobs, but for sake of reliability should we
> > consider splitting the 1st & 3rd jobs. Add --disable-linux-user to both
> > of the existing jobs, and then adding 2 new jobs with --disable-system
> > and --disable-tools set ?
>
> Good idea. I don't suppose you've already tried this?
No, I've not gone beyond quickly writing this previous mail :-)
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 :|
next prev parent reply other threads:[~2018-03-13 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 14:15 [Qemu-devel] [PULL 0/1] Travis speed-up Alex Bennée
2018-02-09 14:15 ` [Qemu-devel] [PULL 1/1] .travis.yml: add --disable-linux-user for some jobs Alex Bennée
2018-03-13 13:40 ` Daniel P. Berrangé
2018-03-13 13:49 ` Paolo Bonzini
2018-03-13 13:53 ` Daniel P. Berrangé
2018-03-13 14:02 ` Alex Bennée
2018-03-13 14:04 ` Daniel P. Berrangé [this message]
2018-02-09 17:44 ` [Qemu-devel] [PULL 0/1] Travis speed-up Peter Maydell
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=20180313140426.GY3048@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).