qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <famz@redhat.com>,
	qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] travis: Split the OSX job
Date: Fri, 09 Nov 2018 12:31:13 +0000	[thread overview]
Message-ID: <87k1lm5t66.fsf@linaro.org> (raw)
In-Reply-To: <20181108160115.20747-1-philmd@redhat.com>


Philippe Mathieu-Daudé <philmd@redhat.com> writes:

> The current OSX job often reach the 50min Travis-CI time limit.
>
> Split it in two jobs, which as of this commit took:
> - system: ~39min
> - user:    ~9min
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>

I suggested a different split in:

  https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg01695.html

Does a user build actually build anything we can run?

> ---
>  .travis.yml | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index aa49c7b114..827f2252b6 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -107,7 +107,11 @@ matrix:
>      - env: CONFIG="--disable-tcg"
>             TEST_CMD=""
>        compiler: gcc
> -    - env: CONFIG=""
> +    # OSX builds
> +    - env: CONFIG="--disable-user"
> +      os: osx
> +      compiler: clang
> +    - env: CONFIG="--disable-system --disable-tools --disable-docs --disable-guest-agent"
>        os: osx
>        compiler: clang
>      # Python builds


--
Alex Bennée

      reply	other threads:[~2018-11-09 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 16:01 [Qemu-devel] [PATCH] travis: Split the OSX job Philippe Mathieu-Daudé
2018-11-09 12:31 ` Alex Bennée [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=87k1lm5t66.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --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).