All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>,
	David Barrera <dbarrera@us.ibm.com>, Li Ge <lge@us.ibm.com>,
	Stephanie Glass <sglass@us.ibm.com>,
	ian.pratt@cl.cam.ac.uk
Subject: RE: New Xentest automated testing framework snapshot
Date: Tue, 01 Mar 2005 17:06:48 -0600	[thread overview]
Message-ID: <1109718408.4911.48.camel@localhost.localdomain> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E336E@liverpoolst.ad.cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]

On Tue, 2005-03-01 at 22:45 +0000, Ian Pratt wrote:
> Folks,
> This work is much appreciated -- many thanks.
> 
> It would be great if someone could set this up to start doing nightly
> builds, tests and benchmarks, and make the results available. It would
> also be useful to do some 'historical' tests too, perhaps running the
> kernel on every Sunday night in the unstable tree all the way back to
> the 2.0. 
That's the idea.  Most of my testing with xentest so far has been for
the purpose of making sure xentest is behaving properly, but this week
(hopefully) I'm going to try to get a few machines in my environment
doing this every night.  It will be LTP initially, but I hope to be
adding more tests and test suites to the mix, and I'm even more hopeful
about either writing, or getting some xen specific tests dropped in my
lap (I know you sent me one a while back, that one is first in the
queue).

As for results, my thoughts were to just do some postprocessing and
results comparison between consecutive runs to see if anything changed,
and examine any new failures to see if they are really bugs or not.  If
you'd like to see more frequent results postings, and it wouldn't be
bothersome, I can see what can be done.

Ideally though, this is most useful if a lot of different people are
running this on a variety of machines.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-01 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 22:45 New Xentest automated testing framework snapshot Ian Pratt
2005-03-01 23:06 ` Paul Larson [this message]
2005-03-02  0:01 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02  0:00 Ky Srinivasan
2005-03-01 22:02 Paul Larson
2005-03-01 22:45 ` Ronald G. Minnich

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=1109718408.4911.48.camel@localhost.localdomain \
    --to=plars@linuxtestproject.org \
    --cc=dbarrera@us.ibm.com \
    --cc=ian.pratt@cl.cam.ac.uk \
    --cc=lge@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=sglass@us.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.