From: Ewan Mellor Subject: Re: [PATCH][RESEND] Fix stale-state issue with 'xm dom{id, name}' Date: Wed, 5 Oct 2005 00:14:09 +0100 Message-ID: <20051004231409.GB16856@uk.xensource.com> References: <87psqqh4ww.fsf@us.ibm.com> <20051004073630.GC4104@linford.intra> <871x31yylz.fsf@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <871x31yylz.fsf@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Oct 04, 2005 at 10:35:04AM -0700, Dan Smith wrote: > EM> I would be grateful if you could re-run xm-test and let me know > EM> how it looks. There might still be some bugs to iron out, but > EM> hopefully you will find that the behaviour under xm-test is much > EM> improved. > > After two runs of xm-test, I'm not seeing failures on either of the > tests that poke specific stale-state issues. That's good news :) > > I'll see about writing some more tests targeted at stale-state > detection, just to make sure ;) Great, thanks a lot Dan, I appreciate it. Ewan.