All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: CACHE_NAME in .travis.yml (was Re: [Qemu-devel] [PATCH 08/10] .travis.yml: Cache Linux/GCC 'debug profile' jobs together)
Date: Wed, 14 Oct 2020 17:46:59 -0400	[thread overview]
Message-ID: <20201014214659.GC5733@habkost.net> (raw)
In-Reply-To: <20190903132649.20226-9-philmd@redhat.com>

I just stumbled upon this when editing .travis.yml, and I'm
trying to understand how the $CACHE_NAME trick is supposed to
work.

If I understood the Travis documentation correctly, all
environment variables will affect the cache id (including
$CONFIG, in the case below).  This would mean the two entries
would still use a different cache even if $CACHE_NAME is the
same.

See, for example:
https://travis-ci.org/github/qemu/qemu/jobs/735738551#L965
https://travis-ci.org/github/qemu/qemu/jobs/735738553#L967

Both build tasks have the same value for $CACHE_NAME, but they
are fetching two different cache URLs:

master/cache--linux-focal-50ba7438064455bdb04bb41dcde2c91c34bb797265fe435b84cee4bae7d9b61d--compiler-gcc.tgz
master/cache--linux-focal-8991cfc9b7f3f268e7e50aff4218daa4c206597ae796c60643a84ed58bba0cfb--compiler-gcc.tgz


On Tue, Sep 03, 2019 at 03:26:47PM +0200, Philippe Mathieu-Daudé wrote:
> These jobs build different components but use the same
> host features. Put them in the same cache bucket.
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
>  .travis.yml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index c64a551829..e362c3fe02 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -120,11 +120,13 @@ matrix:
>  
>      - env:
>          - CONFIG="--enable-debug --enable-debug-tcg --disable-user"
> +        - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-debug"
>  
>  
>      # TCG debug can be run just on it's own and is mostly agnostic to user/softmmu distinctions
>      - env:
>          - CONFIG="--enable-debug-tcg --disable-system"
> +        - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-debug"
>  
>  
>      - env:
> -- 
> 2.20.1
> 
> 

-- 
Eduardo



  reply	other threads:[~2020-10-14 21:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 13:26 [Qemu-devel] [PATCH 00/10] travis: Use caching when possible Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 01/10] .travis.yml: Enable multiple caching features Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 02/10] .travis.yml: Increase cache timeout from 3min to 20min Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 03/10] .travis.yml: Cache Python PIP packages Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 04/10] .travis.yml: Cache Avocado cache Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 05/10] .travis.yml: Improve ccache use Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 06/10] .travis.yml: Enable ccache on OSX Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 07/10] .travis.yml: Document how the build matrix use caches Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 08/10] .travis.yml: Cache Linux/GCC 'debug profile' jobs together Philippe Mathieu-Daudé
2020-10-14 21:46   ` Eduardo Habkost [this message]
2019-09-03 13:26 ` [Qemu-devel] [PATCH 09/10] .travis.yml: Cache Linux/GCC 'non-debug " Philippe Mathieu-Daudé
2019-09-03 13:26 ` [Qemu-devel] [PATCH 10/10] .travis.yml: Cache Linux/Clang " Philippe Mathieu-Daudé
2019-09-04 11:26 ` [Qemu-devel] [PATCH 00/10] travis: Use caching when possible Alex Bennée

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=20201014214659.GC5733@habkost.net \
    --to=ehabkost@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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.