From: Daniel Stekloff <dsteklof@us.ibm.com>
To: "Yu, Ping Y" <ping.y.yu@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: xm-test failures?
Date: Wed, 15 Mar 2006 07:01:31 -0800 [thread overview]
Message-ID: <1142434892.5339.4.camel@localhost.localdomain> (raw)
In-Reply-To: <2BF508F394C196468CCBEC031320DCDFA9DF08@pdsmsx405>
On Wed, 2006-03-15 at 16:23 +0800, Yu, Ping Y wrote:
> >From our test in VMX, it is fine in latest change set 9238.
Anthony was referring to non-HVM testing, which is seeing failures with
block-attach and migrate tests. These tests are SKIP'd on HVM because it
needs infrastructure for block-attach that isn't there yet and migrate
won't yet work with HVM.
You are right, HVM passes the tests well it does run. Yesterday on
cs9236, I ran with only 3 XFAILS - the network ping tests that are known
problems - as the only errors.
So, it's time to add more tests and support for HVM in xm-test. Any help
is appreciated.
Thanks,
Dan
> >-----Original Message-----
> >From: xen-devel-bounces@lists.xensource.com
> >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Anthony Liguori
> >Sent: 2006年3月15日 7:06
> >To: xen-devel
> >Subject: [Xen-devel] xm-test failures?
> >
> >There seems to be a large number of xm-test failures in current tip. Is
> >anyone else seeing this (~15 FAILs). I'm attempting to figure out what
> >changeset broke things.
> >
> >Regards,
> >
> >Anthony Liguori
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-03-15 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 8:23 xm-test failures? Yu, Ping Y
2006-03-15 15:01 ` Daniel Stekloff [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 23:05 Anthony Liguori
2006-03-15 15:31 ` Paul Larson
2006-03-15 17:31 ` Paul Larson
2006-03-15 18:31 ` Anthony Liguori
2006-03-15 18:40 ` Ewan Mellor
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=1142434892.5339.4.camel@localhost.localdomain \
--to=dsteklof@us.ibm.com \
--cc=ping.y.yu@intel.com \
--cc=xen-devel@lists.xensource.com \
/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.