xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <dunlapg@umich.edu>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Anshul Makkar <anshul.makkar@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: xenbits "official" repo for XTF (was Re: [PATCH 0/2] xtf: add launcher (+1 bugfix)
Date: Tue, 14 Jun 2016 18:27:05 +0100	[thread overview]
Message-ID: <db32a341-48e3-cc03-8c72-35671bf36193@citrix.com> (raw)
In-Reply-To: <22366.48912.679914.484689@mariner.uk.xensource.com>

On 13/06/16 15:11, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] xenbits "official" repo for XTF (was Re: [PATCH 0/2] xtf: add launcher (+1 bugfix)"):
>> On Mon, Jun 13, 2016 at 11:10 AM, Andrew Cooper
>>> I am not completely averse to changing it, but I don't see an
>>> alternative which is any better or clearer.
>> Do you have any opinions on "Xen verification framework"?
> The problem IMO is the word "framework" which implies some kind of
> daemonic machinery.

I disagree.  Framework implies building blocks.

I can't see any implication or suggestion of daemonic machinery here.

> The frameworky bit of XTF is quite small; mostly,
> it is a suite of test cases.  "Xen Micro-VM Test Suite" maybe ?

At the moment, the framework is larger than the suite, although I don't
necessarily expect this to remain the case.  Having said that, I would
argue that the "framework" is the more important part; It is the bit
with the complicated logic to build the same code into multiple
different VM types, and APIs to make test reporting easy and consistent.

>
> (I think "verification" is inaccurate because to me it implies formal
> methods, static analysis, or the like.)

I concur.  "verification" is definitely a less accurate description.

>
>> If we weren't going to change it, then you should probably put a note
>> somewhere near the top of the introduction saying something like, "If
>> you're looking for the Xen automated push-gate software, you want
>> osstest[link]", so that people who want osstest but search for "xen
>> test framework" find what they're looking for.
> "CI (continuous integration)" is the keyword that many people will
> have for osstest.
>
> I would suggest
>
>   (This is not the Xen Project's CI / Continuous Integration /
>    automated push gate system.  For that, see
>    <a href="wiki">osstest</a>.)
>
> or something.

I am happy to add text to that effect.

~Andrew



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-06-14 17:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 13:46 [PATCH 0/2] xtf: add launcher (+1 bugfix) Roger Pau Monne
2016-05-19 13:46 ` [PATCH 1/2] xtf: remove setting ROOT path in common.mk Roger Pau Monne
2016-05-19 13:52   ` Andrew Cooper
2016-05-19 13:46 ` [PATCH 2/2] xtf: add a launcher script Roger Pau Monne
2016-06-09 15:04 ` xenbits "official" repo for XTF (was Re: [PATCH 0/2] xtf: add launcher (+1 bugfix) Ian Jackson
2016-06-13  8:59   ` George Dunlap
2016-06-13 10:10   ` Andrew Cooper
2016-06-13 14:03     ` George Dunlap
2016-06-13 14:11       ` Ian Jackson
2016-06-14 17:27         ` Andrew Cooper [this message]
2016-06-15  8:31           ` George Dunlap
2016-06-20 17:03             ` Ian Jackson
2016-06-20 17:10               ` Konrad Rzeszutek Wilk
2016-06-21 10:17               ` Wei Liu
2016-06-21 10:36               ` David Vrabel
2016-06-21 10:42                 ` Ian Jackson
2016-07-01 19:04                 ` Ian Jackson
2016-07-06 11:19                   ` Lars Kurth
2016-07-06 14:22                     ` Konrad Rzeszutek Wilk
2016-07-07 11:10                       ` Lars Kurth
2016-07-07 11:26                         ` Andrew Cooper
2016-07-07 13:59                           ` Ian Jackson
2016-07-07 14:02                             ` David Vrabel
2016-07-07 14:58                               ` Ian Jackson
2016-07-07 15:00                                 ` Ian Jackson
2016-07-07 14:11                             ` Andrew Cooper
2016-07-07 17:17                               ` Lars Kurth
2016-07-08 13:06                                 ` Andrew Cooper
2016-07-08 13:42                                   ` Lars Kurth
2016-07-08 13:48                                     ` Andrew Cooper
2016-07-12 15:13                                   ` George Dunlap
2016-07-15 10:21                                 ` Ian Jackson
2016-07-15 10:49                                   ` Lars Kurth
2016-07-18 14:36                                     ` Ian Jackson
2016-07-18 15:19                                       ` Lars Kurth
2016-07-18 15:30                                         ` Ian Jackson
2016-07-18 15:36                                           ` Lars Kurth
2016-07-18 15:58                                             ` Ian Jackson
2016-07-18 16:06                                               ` Lars Kurth
2016-07-18 15:31                                         ` Ian Jackson
2016-08-08 17:04                                   ` Ian Jackson
2016-07-07 15:22                           ` Konrad Rzeszutek Wilk
2016-06-14 17:01   ` Konrad Rzeszutek Wilk

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=db32a341-48e3-cc03-8c72-35671bf36193@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=anshul.makkar@citrix.com \
    --cc=dunlapg@umich.edu \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).