xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	keir.xen@gmail.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: [RFC 0 PATCH 3/3] PVH dom0: construct_dom0 changes
Date: Wed, 9 Oct 2013 15:37:41 +0100	[thread overview]
Message-ID: <52556A35.1070804@citrix.com> (raw)
In-Reply-To: <52555732.5060907@eu.citrix.com>

On 09/10/13 14:16, George Dunlap wrote:
> On 09/10/13 14:13, Andrew Cooper wrote:
>> On 09/10/13 14:02, George Dunlap wrote:
>>> On 10/08/2013 01:30 PM, Konrad Rzeszutek Wilk wrote:
>>>> These issues sprang up with your patches,  not with the ones that
>>>> Mukesh posted ? Which did get tested for regression and passed with
>>>> flying colours? That means there is a working baseline. Would that
>>>> help?
>>>> Mukesh do you have any ideas what might be amiss?
>>> The issues with the code motion patch are almost certainly mine.  Andy
>>> Cooper ran one of Mukesh's versions through one of the XenRT tests
>>> (probably a nightly) and it came up fine.  I just need to go through
>>> and figure out what I messed up.
>> I ran Mukesh's v10 series through a XenServer BST, which confirmed no
>> glaring function regressions in PV and HVM domains.
>
> I'm not sure anyone outside the XenServer team knows what a "BST"
> might entail. :-)  Is that "Basic Smoke Test"?  "Build Sanity Test"? 
> "Big Stress Test"?
>
>  -George

For those interested, XenRT is the test system for XenServer, and has
several categories.

The first is the BVT - "Basic Verification Test".  This does install,
and running a single test from each of the primary areas (e.g. single PV
vm, single HVM vm, one migrate, one vlan, etc).  This test is performed
automatically on all code submission.

The next is the BST - "Branch Safety Test".  This is a substantially
larger set of basic functional tests.  It is 5-8 hours to run and is run
as-and-when a developer decides they have put in a large chunk of work
and want rather more testing than a BVT, but don't want to commit the
resources of a nightly on something which might crash and burn.

The third is the Nightly test.  This is 2.5K tests taking ~16h and ~150
machines, which is a fairly comprehensive test of XenServer.

Beyond that there are sets of tests run less often, including the
nightly and weekend stress tests.

~Andrew

  reply	other threads:[~2013-10-09 14:37 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 21:03 [RFC 0 PATCH 0/3]: PVH dom0 construction Mukesh Rathor
2013-09-25 21:03 ` [RFC 0 PATCH 1/3] PVH dom0: create domctl_memory_mapping() function Mukesh Rathor
2013-09-26  7:03   ` Jan Beulich
2013-09-25 21:03 ` [RFC 0 PATCH 2/3] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-09-26  7:21   ` Jan Beulich
2013-09-26 23:32     ` Mukesh Rathor
2013-09-25 21:03 ` [RFC 0 PATCH 3/3] PVH dom0: construct_dom0 changes Mukesh Rathor
2013-09-26  8:02   ` Jan Beulich
2013-09-27  0:17     ` Mukesh Rathor
2013-09-27  6:54       ` Jan Beulich
2013-10-03  0:53         ` Mukesh Rathor
2013-10-04  6:53           ` Jan Beulich
2013-10-04 13:35             ` Konrad Rzeszutek Wilk
2013-10-04 14:05               ` Jan Beulich
2013-10-04 16:02                 ` Konrad Rzeszutek Wilk
2013-10-04 16:07                   ` Jan Beulich
2013-10-04 20:59                     ` Konrad Rzeszutek Wilk
2013-10-05  1:06                       ` Mukesh Rathor
2013-10-07  7:12                         ` Jan Beulich
2013-10-08  0:58             ` Mukesh Rathor
2013-10-08  7:51               ` Jan Beulich
2013-10-08  8:03                 ` Jan Beulich
2013-10-08  9:39                   ` George Dunlap
2013-10-08  9:57                     ` Jan Beulich
2013-10-08 10:01                       ` George Dunlap
2013-10-08 10:19                         ` Lars Kurth
2013-10-08 12:30                     ` Konrad Rzeszutek Wilk
2013-10-09 13:02                       ` George Dunlap
2013-10-09 13:13                         ` Andrew Cooper
2013-10-09 13:16                           ` George Dunlap
2013-10-09 14:37                             ` Andrew Cooper [this message]
2013-10-09 17:50                       ` Tim Deegan
2013-10-09 22:31                         ` Mukesh Rathor
2013-09-27  1:55     ` Mukesh Rathor
2013-09-27  7:01       ` Jan Beulich
2013-09-27 23:03         ` Mukesh Rathor
2013-09-30  6:56           ` Jan Beulich
2013-10-08  0:52             ` Mukesh Rathor
2013-10-08  7:43               ` Jan Beulich
2013-10-09 21:59                 ` Mukesh Rathor

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=52556A35.1070804@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=keir.xen@gmail.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).