All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: ian.jackson@eu.citrix.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v3] ts-libvirt-build: use Osstest::BuildSupport::submodulefixup
Date: Tue, 6 Jan 2015 13:54:43 +0000	[thread overview]
Message-ID: <1420552483.28863.159.camel@citrix.com> (raw)
In-Reply-To: <1420473183.28863.46.camel@citrix.com>

On Mon, 2015-01-05 at 15:53 +0000, Ian Campbell wrote:
> On Mon, 2015-01-05 at 15:36 +0000, Ian Campbell wrote:
> > Instead of cloning gnulib manually which can break if upstream gnulib
> > gets ahead of libvirt.git (which applies patches on the fly etc). By
> > using submodulefixup we automatically DTRT and use the version of
> > gnulib specified by the libvirt.git submodule metadata, but with a
> > runvar override if necessary.
> > 
> > This also removes a whole bunch of faffing in ap-*, cr-daily-branch
> > and mfi-common to get the version of gnulib to use, which was always a
> > bit of a wart (ungated for one thing...).
> > 
> > We continue to use --no-git and GNULIB_SRCDIR because otherwise
> > autogen.sh (via bootstrap) will force its own version, overwriting
> > what submodulefixup has done. For this we need a way to get the hash
> > representing the module, so introduce submodule_find (and rework
> > submodule_have in terms of it).
> > 
> > Tested in standalone mode with build-amd64-libvirt and
> > build-amd64-rumpuserxen (because I touched submodule_have, AFAICT the
> > bodges were not run). The libvirt build was tested both with the
> > automatic revisions and with:
> >     revision_libvirt=2360fe5d24175835d3f5fd1c7e8e6e13addab629
> >     revision_libvirt_gnulib=16518d9ed8f25d3e53931dd1aa343072933e4604
> > (used in successful libvirt flight 32648), in both cases confirming
> > that the build used the desired versions.
> > 
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> 
> Ian J acked on IRC so I have pushed to osstests' pretest branch.

The flight which tested this had a couple of fails, but everything
related to this change passed, so after consulting with Ian J I force
pushed this changeset and killed all the inprogress jobs (none of which
could have passed). Any new flights have a chance of passing again now.

Ian.

      reply	other threads:[~2015-01-06 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  9:42 [xen-unstable test] 33083: regressions - FAIL xen.org
2015-01-05 10:17 ` Ian Campbell
2015-01-05 13:03   ` [PATCH OSSTEST] ts-libvirt-build: use Osstest::BuildSupport::submodulefixup Ian Campbell
2015-01-05 15:08   ` [PATCH OSSTEST v2] " Ian Campbell
2015-01-05 15:36   ` [PATCH OSSTEST v3] " Ian Campbell
2015-01-05 15:53     ` Ian Campbell
2015-01-06 13:54       ` Ian Campbell [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=1420552483.28863.159.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xen.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.