From: George Dunlap <george.dunlap@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Call to write tests for osstest
Date: Wed, 14 Aug 2013 14:52:31 +0100 [thread overview]
Message-ID: <520B8B9F.3080006@eu.citrix.com> (raw)
In-Reply-To: <20130808194044.GE4513@konrad-lan.dumpdata.com>
On 08/08/13 20:40, Konrad Rzeszutek Wilk wrote:
> On Thu, Aug 08, 2013 at 05:01:01PM +0100, George Dunlap wrote:
>> As release coordinator, and therefore de-facto
>> tracker-of-bugs-and-regressions, it seems to me that one of the
>> shortcomings in our current development mode is a lack of good
>> regression testing for many of the less common, but still very
>> important features of Xen; things like S3, driver domains, nested
>> virt, and so on.
>>
>> We do have a regression-testing push gate for the xen trees, written
>> by Ian Jackson, called osstest, with a lot of great functionality,
>> including a test scheduler, an automatic Baysean bisector, and so on.
>> Apart from more hardware, it is mainly lacking a more complete set of
>> tests.
>>
>> The Xen Project team here at Citrix agreed with me, and have decided
>> during the 4.4 timeframe to take on the task of adding some important
>> functional tests to osstest; our list is below. We'd love for you to
>> join us.
>>
>> I will be tracking the implementation of the tests as part of the
>> regular 4.4 release updates. I encourage people to join us by
>> thinking about a particular feature or bit of functionality that is
>> not yet tested by osstest, which you would like to see implemented in
>> the 4.4 timeframe, and responding to this e-mail, or one of the
>> regular development update e-mails asking it to be added.
>>
>> There is a description of osstest, along with a link to the source code, here:
>>
>> http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-osstest/
>>
>> === Testing coverage ===
>>
>> * Network driver domains
>> @George
>>
>> * new libxl w/ previous versions of xl
>> @IanJ
>>
>> * Host S3 suspend
>> @bguthro?
>>
>> * Default [example] XSM policy
>> @Stefano to ask Daniel D
>>
>> * Xen on ARM
>> # problem ATM: hardware
>> @ianc
>> emulator: @stefano to think about it
>>
>> * Storage driver domains
>> @roger
>>
>> * HVM pci passthrough
>> @anthony
> PV pci passthrough would be nice too.
>
> You can assign me to it, thought I would need some help in groking the
> osstest thingy. Maybe I will just copy what @anthony is doing.
I was thinking that would be a subset of the Network driver domains --
but I'll add it on here, and whoever gets to it first can do it. :-)
-George
next prev parent reply other threads:[~2013-08-14 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 16:01 Call to write tests for osstest George Dunlap
2013-08-08 17:32 ` Sander Eikelenboom
2013-08-08 19:42 ` Konrad Rzeszutek Wilk
2013-08-09 11:19 ` Dario Faggioli
2013-08-09 11:46 ` Sander Eikelenboom
2013-08-09 12:00 ` Wei Liu
2013-08-09 12:04 ` Sander Eikelenboom
2013-08-09 12:16 ` Dario Faggioli
2013-08-14 15:03 ` George Dunlap
2013-08-08 17:37 ` Sander Eikelenboom
2013-08-14 13:51 ` George Dunlap
2013-08-08 19:40 ` Konrad Rzeszutek Wilk
2013-08-14 13:52 ` George Dunlap [this message]
2013-08-13 14:24 ` Ben Guthro
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=520B8B9F.3080006@eu.citrix.com \
--to=george.dunlap@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 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).