From: Paul Larson <plars@linuxtestproject.org>
To: xen-devel <xen-devel@lists.sourceforge.net>
Cc: Li Ge <lge@us.ibm.com>, David Barrera <dbarrera@us.ibm.com>
Subject: Xen automated testing framework
Date: Fri, 21 Jan 2005 16:17:17 -0600 [thread overview]
Message-ID: <1106345838.8950.247.camel@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 715 bytes --]
We're starting to work on an automated build and test tool for Xen,
mainly for the purpose of conveniently allowing automated nightly
testing so that bugs can be found and fixed quickly.
Right now it's not terribly useful and doesn't do error checking, but is
more of a proof of concept. If anyone has any ideas or suggestions
about this, please let me know. I'd like to get some feedback before
going too far, so that it can be made useful for more people. It should
eventually contain init scripts to kick off the tests, support more
domains, and gather the results via something like scp or a shared
mount.
--
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org
[-- Attachment #1.2: xentest.tgz --]
[-- Type: application/x-compressed-tar, Size: 2621 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-21 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 22:17 Paul Larson [this message]
2005-01-21 22:21 ` Xen automated testing framework Ronald G. Minnich
2005-01-21 22:29 ` Paul Larson
2005-01-21 22:48 ` Ronald G. Minnich
2005-01-21 22:35 ` Li Ge
-- strict thread matches above, loose matches on Subject: below --
2005-01-21 22:58 Ian Pratt
2005-01-21 23:07 ` Paul Larson
2005-01-22 8:38 ` Ian Pratt
2005-01-22 15:43 ` David Hopwood
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=1106345838.8950.247.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=dbarrera@us.ibm.com \
--cc=lge@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.