xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: rumpkernel-users@lists.sourceforge.net,
	xen-devel@lists.xensource.com, Antti Kantee <pooka@iki.fi>
Subject: Re: [OSSTEST PATCH] rump kernel tests: Get upstream from rumprun-xen
Date: Thu, 31 Jul 2014 15:58:58 +0100	[thread overview]
Message-ID: <E1XCrsD-0000Fs-CV@sfs-ml-4.v29.ch3.sourceforge.com> (raw)
In-Reply-To: <1406818576-16423-1-git-send-email-ian.jackson@eu.citrix.com>

On Thu, 2014-07-31 at 15:56 +0100, Ian Jackson wrote:
> Replace https://github.com/rumpkernel/rumpuser-xen
> with https://github.com/rumpkernel/rumprun-xen
> as the source for the pre-test version.  The repo has been renamed
> upstream.
> 
> We do not change, at this time:
> 
>  * The name of the post-test output repo on xenbits,
>      git://xenbits.xen.org/rumpuser-xen.git#xen-tested-master
> 
> Changing those would be a bit fiddly.
> 
> And we don't change the following, which contain `rumpuserxen':
> 
>  * osstest `branch', `recipe', and `jobs' which are used to correlate
>    and specify aspects of the different production test runs of
>    different versions of the code.  The branch name appears in the
>    Subject lines of email reports, and the job names in the body (and
>    as column names in the html test report matrix).
> 
>  * The osstest `tree' names (which are used to specify and correlate
>    the different versions and urls of the `same' codebase in the
>    various tests).  Also, we leave unchanged the corresponding
>    osstest tree plumbing environment variable names.
> 
>  * The osstest build output identifiers from ts-rumpuser-xen-build
>    including the runvar name and the dist part name.  (These are used
>    to communicate between the build and test jobs.)
> 
> Changing those would break cross-change comparison of test results and
> osstest's automatic bisection across the change.
> 
> We also don't change:
> 
>   * The names of the ts-rumpuserxen-* test scripts.
> 
> While this could be changed by renaming the files and editing
> sg-run-job to match, it doesn't seem sensible to rename these while
> leaving everything else unchanged.
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>



------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk

      parent reply	other threads:[~2014-07-31 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <21466.21735.6720.603455@chiark.greenend.org.uk>
2014-07-31 14:56 ` [OSSTEST PATCH] rump kernel tests: Get upstream from rumprun-xen Ian Jackson
2014-07-31 14:56 ` Ian Jackson
     [not found] ` <1406818576-16423-1-git-send-email-ian.jackson@eu.citrix.com>
2014-07-31 14:58   ` Ian Campbell
2014-07-31 14:58   ` 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=E1XCrsD-0000Fs-CV@sfs-ml-4.v29.ch3.sourceforge.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=pooka@iki.fi \
    --cc=rumpkernel-users@lists.sourceforge.net \
    --cc=xen-devel@lists.xensource.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 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).