qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] QEMU travis builds: can we move the preseed tarball to qemu.org ?
Date: Tue, 25 Apr 2017 16:32:06 +0100	[thread overview]
Message-ID: <20170425153206.GM21129@redhat.com> (raw)
In-Reply-To: <87bmrkbjdp.fsf@linaro.org>

On Tue, Apr 25, 2017 at 04:24:18PM +0100, Alex Bennée wrote:
> 
> Daniel P. Berrange <berrange@redhat.com> writes:
> 
> > On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
> >> Hi; a recent travis build failure made me notice that our .travis.yml
> >> config references a preseed tarball from here:
> >> http://people.linaro.org/~alex.bennee/qemu-submodule-git-seed.tar.xz
> >>
> >> I think this is a bit less than ideal -- we should really be hosting
> >> this on qemu.org. Can we arrange to move it?
> >
> > I'm curious how much speed difference there is in seeding the git submodules
> > in this way vs letting git pull down from git.qemu.org directly ?
> 
> It was quite high from what I recall, exacerbated by the fact we have
> quite so many submodules. Unfortunately it doesn't seem that easy to go
> back in the history of the tests to find out so I'll have to re-run the
> test:
> 
>   https://travis-ci.org/stsquad/qemu/builds/225648653
> 
> So roughly 62s without a seed vs 15s with. I presume the seed is also
> cached by Travis's web-caching.

Wow, yes, that is quite a difference !

I wonder if Travis' arbitrary sub-dir caching feature would help us to
the same extent, while avoiding need to manually maintain the preseed.

  https://docs.travis-ci.com/user/caching/

It just caches entire content of a given subdir between runs. First time
it would be slow, but presumably fast thereafter, and any time the submodule
gets new updates, those would get cached too

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:[~2017-04-25 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 14:51 [Qemu-devel] QEMU travis builds: can we move the preseed tarball to qemu.org ? Peter Maydell
2017-04-25 14:58 ` Daniel P. Berrange
2017-04-25 15:24   ` Alex Bennée
2017-04-25 15:32     ` Daniel P. Berrange [this message]
2017-04-25 15:54       ` Alex Bennée
2017-04-25 16:19         ` Jeff Cody
2017-04-25 15:10 ` 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=20170425153206.GM21129@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=jcody@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).