qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	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 13:53:05 +0000	[thread overview]
Message-ID: <20180313135305.GX3048@redhat.com> (raw)
In-Reply-To: <2f452164-d9d7-80ae-c5fe-bdc1889633f8@redhat.com>

On Tue, Mar 13, 2018 at 02:49:42PM +0100, Paolo Bonzini wrote:
> On 13/03/2018 14:40, Daniel P. Berrangé wrote:
> >> @@ -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 :-(
> > 
> > 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 ?
> 
> Out of curiosity, why do we need the third job at all?  And
> --enable-trace-backends=log is the default, so "--enable-debug
> --enable-debug-tcg" should be enough.

Presumably that is intended to validate that code still builds correctly
when various optional features are turned off, by exercising different
codepaths in the countless #ifdef HAVE_$FEATURE  conditionals we have.

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 :|

  reply	other threads:[~2018-03-13 13:53 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é [this message]
2018-03-13 14:02     ` Alex Bennée
2018-03-13 14:04       ` Daniel P. Berrangé
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=20180313135305.GX3048@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=pbonzini@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).