From: Ewan Mellor <ewan@xensource.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Xen-devel@lists.xensource.com, marvel@us.ibm.com,
Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH] Repost - xm lists display and formatting
Date: Fri, 17 Feb 2006 14:32:04 -0800 [thread overview]
Message-ID: <20060217223204.GK3848@localhost.localdomain> (raw)
In-Reply-To: <43F64CD8.3090106@us.ibm.com>
On Fri, Feb 17, 2006 at 02:23:20PM -0800, Nivedita Singhvi wrote:
> Ewan, are you still running xm-test as part of your pre-commit
> regression testing?
Yes, we run the xm-test quick run before the change gets pushed from our
staging tree to xen-unstable, and the xm-test full run overnight (on
many machines).
> Also, have you started running on hvm hw?
James has been working on that recently. It looks from the XenRT matrix
that it's not there yet, but it certainly will be soon.
> We'd like to see more of these bugs caught prior to commit,
> and hoping to encourage all the developers out there to
> please run as well...
That's what the staging tree is for -- if there was any breakage (which
it turns out that there wasn't) then the change would never have been
pushed to the public unstable tree. My email was a plea for someone to
improve the comprehensiveness of xm-test, now that we have a new
feature.
Ewan.
next prev parent reply other threads:[~2006-02-17 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 16:22 [PATCH] Repost - xm lists display and formatting Stefan Berger
2006-02-17 18:41 ` Ewan Mellor
2006-02-17 19:00 ` Daniel Stekloff
2006-02-17 19:17 ` Stefan Berger
2006-02-17 20:01 ` Woody Marvel
2006-02-17 19:54 ` Woody Marvel
2006-02-17 20:45 ` Stefan Berger
2006-02-17 22:03 ` Stefan Berger
2006-02-17 22:23 ` Nivedita Singhvi
2006-02-17 22:32 ` Ewan Mellor [this message]
2006-02-17 22:36 ` Nivedita Singhvi
2006-02-17 23:51 ` Woody Marvel
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=20060217223204.GK3848@localhost.localdomain \
--to=ewan@xensource.com \
--cc=Xen-devel@lists.xensource.com \
--cc=marvel@us.ibm.com \
--cc=niv@us.ibm.com \
--cc=stefanb@us.ibm.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.