All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v4 4/6] .travis.yml: enable ccache for the builds
Date: Thu, 04 Feb 2016 15:09:03 +0000	[thread overview]
Message-ID: <87twloo6ls.fsf@linaro.org> (raw)
In-Reply-To: <20160203055948.GO15080@voom.fritz.box>


David Gibson <david@gibson.dropbear.id.au> writes:

> On Tue, Feb 02, 2016 at 05:34:06PM +0000, Alex Bennée wrote:
>> Travis support ccache on a cache-per-branch basis. Given not much of the
>> build changes between pushes as well as the duplication in each build it
>> seems worthwhile enabling this.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Tested-by: David Gibson <david@gibson.dropbear.id.au>
>
> From the build times, it doesn't look like this is buying us as much
> as I might have hoped, still it's unlikely to hurt.
>
> Do we know what the lifetime for the cache travis imposes?

AFAICT they last forever unless the user wipes the cache. They may have a
hidden heuristic to stop them growing too big but I don't know.

>
>> ---
>>  .travis.yml | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index 021eec7..4f09909 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -5,6 +5,7 @@ python:
>>  compiler:
>>    - gcc
>>    - clang
>> +cache: ccache
>>  addons:
>>    apt:
>>      packages:


--
Alex Bennée

  reply	other threads:[~2016-02-04 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 17:34 [Qemu-devel] [PATCH v4 0/6] Travis updates Alex Bennée
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 1/6] .travis.yml: migrate to container builds Alex Bennée
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 2/6] .travis.yml: run make check for all matrix targets Alex Bennée
2016-02-03  5:57   ` David Gibson
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 3/6] .travis.yml: enable each of the co-routine backends Alex Bennée
2016-02-03  5:58   ` David Gibson
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 4/6] .travis.yml: enable ccache for the builds Alex Bennée
2016-02-03  5:59   ` David Gibson
2016-02-04 15:09     ` Alex Bennée [this message]
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 5/6] .travis.yml: reduce the test matrix a little Alex Bennée
2016-02-03  6:00   ` David Gibson
2016-02-02 17:34 ` [Qemu-devel] [PATCH v4 6/6] MAINTAINERS: Add .travis.yml Alex Bennée
2016-02-03  6:01   ` David Gibson

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=87twloo6ls.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.