All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: David F Barrera <dfbp@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH][XM-TEST] Fix bugzilla # 674 by changing the xm-test	Console.py to wait for the command prompt.
Date: Mon, 19 Jun 2006 00:02:44 +0100	[thread overview]
Message-ID: <1150671764.10120.7.camel@localhost.localdomain> (raw)
In-Reply-To: <44930F5C.4040700@us.ibm.com>

On Fri, 2006-06-16 at 15:06 -0500, David F Barrera wrote:
> Harry,
> 
> I tested your patch on two machines--lots of failures, not sure related 
> to your changes. Attached are the logs.

Quite a lot of the failures are from Thursday which was before I wrote
the patch so I think there is a good chance that those are not related.
Of the remainder, I there is one instance of a "timed out waiting for
console prompt" which is the new timeout in my patch but this is for the
memset_random test which fails for me for a different reason so the
timeout is probably correct in this case.

The remainder seem to be completely unrelated.  So, I think my patch is
probably good and the rest of your problems are probably just more
issues in the xm-test code or possibly real bugs.

Harry

  reply	other threads:[~2006-06-18 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 18:49 [PATCH][XM-TEST] Fix bugzilla # 674 by changing the xm-test Console.py to wait for the command prompt Harry Butterworth
2006-06-16 20:06 ` David F Barrera
2006-06-18 23:02   ` Harry Butterworth [this message]
2006-06-16 20:35 ` David F Barrera
2006-06-19 16:17 ` David F Barrera
  -- strict thread matches above, loose matches on Subject: below --
2006-06-19 16:36 Harry Butterworth

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=1150671764.10120.7.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=dfbp@us.ibm.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.