All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v4] OSSTEST: introduce a raisin build test
Date: Mon, 18 May 2015 14:46:14 +0100	[thread overview]
Message-ID: <1431956774.4944.63.camel@citrix.com> (raw)
In-Reply-To: <21849.59920.558279.892547@mariner.uk.xensource.com>

On Mon, 2015-05-18 at 14:33 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH v4] OSSTEST: introduce a raisin build test"):
> > On Mon, 2015-05-18 at 14:05 +0100, George Dunlap wrote:
> > > That solves the most general case; but it sounds like you care mostly
> > > about the very specific case of dealing with components that depend on
> > > the current output of xen.git.  Starting simple may be fine.
> > 
> > Currently we only have ts-*-build things which depend on the output of
> > ts-xen-build (in fact, we only have ts-libvirt-build).
> 
> That's not true.  We have:
> 
>  job                      step               script
> 
>  build-amd64              xen-build          ts-xen-build
>  build-amd64-rumpuserxen  rumpuserxen-build  ts-rumpuserxen-build
>  build-amd64-rumpuserxen  xen-build          ts-xen-build 
> 
> where each of the lines in my table, above, uses output from the
> previous line.

Indeed, I even seem to have partially remembered that in the next para
(partially because I had it as in the future...)

Ian.

  reply	other threads:[~2015-05-18 13:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12  9:20 [PATCH v4] OSSTEST: introduce a raisin build test Stefano Stabellini
2015-05-12 10:12 ` Ian Campbell
2015-05-12 11:16   ` Ian Jackson
2015-05-12 11:20   ` Stefano Stabellini
2015-05-12 11:33     ` Ian Campbell
2015-05-12 11:46       ` Stefano Stabellini
2015-05-13  9:01         ` Ian Campbell
2015-05-13 11:48           ` Stefano Stabellini
2015-05-13 11:57             ` Ian Campbell
2015-05-18 10:08             ` George Dunlap
2015-05-18 10:33               ` Ian Campbell
2015-05-18 10:54                 ` George Dunlap
2015-05-18 11:21                   ` Ian Campbell
2015-05-18 13:05                     ` George Dunlap
2015-05-18 13:14                       ` Ian Campbell
2015-05-18 13:23                         ` George Dunlap
2015-05-18 13:32                           ` Ian Campbell
2015-05-18 13:33                         ` Ian Jackson
2015-05-18 13:46                           ` Ian Campbell [this message]
2015-06-17 14:13                       ` Stefano Stabellini

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=1431956774.4944.63.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.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.