public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, KVM List <kvm@vger.kernel.org>,
	Uri Lublin <uril@redhat.com>
Subject: Re: kvm-autotest -- introducing kvm_runtest_2
Date: Wed, 11 Mar 2009 15:58:22 -0500	[thread overview]
Message-ID: <20090311205822.GX11777@us.ibm.com> (raw)
In-Reply-To: <1162609922.1515021236758503416.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>

* Michael Goldish <mgoldish@redhat.com> [2009-03-11 03:02]:
> > We've also been creating stepfiles for Linux guests as well that
> > aren't
> > here, various SLES and RHEL installs -- and I've repeatedly seen the
> > same issue where the cropped region *should* match but isn't, and it
> > isn't a result of any of the very correct reasons you've listed below
> > as
> > to why the stepfiles might fail.

[snip]

> 
> Regarding the stepfiles you created for Linux -- I can't help much
> with those since I don't have the data. I do believe that if I had the
> data and the stepfiles I could quickly identify the problem, so if you
> think those can be sent to us, I'd like to have them.

I created a stepfile for RHEL5 and what I'm seeing is that one of the
screens I captured in stepmaker ended up having a focus ring around
something and on replay the focus isn't there.  This situation isn't
something that a new algo will fix as you pointed out.  I'm wondering if
this is something you've seen.  I don't quite understand how it would
happen since stepmaker and the replace send the same keystrokes.  I also
don't see how in general this can be avoided.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  parent reply	other threads:[~2009-03-11 20:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1170652852.1514931236758361795.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-11  8:01 ` kvm-autotest -- introducing kvm_runtest_2 Michael Goldish
2009-03-11 13:12   ` Ryan Harper
2009-03-11 20:58   ` Ryan Harper [this message]
     [not found] <337817070.1631851236866509897.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-12 14:03 ` Michael Goldish
2009-03-12 14:21   ` Ryan Harper
     [not found] <316573781.1616221236842323850.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-12  7:25 ` Michael Goldish
2009-03-12 12:54   ` Ryan Harper
     [not found] <1419870903.1471901236736357942.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-11  1:54 ` Michael Goldish
2009-03-11  2:58   ` Ryan Harper
     [not found] <160776987.914431236209784966.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-04 23:52 ` Uri Lublin
     [not found] <1786372222.913761236208477884.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-03-04 23:25 ` Uri Lublin
2009-03-01 19:09 Uri Lublin
2009-03-02 17:45 ` Ryan Harper
2009-03-04  8:58   ` Uri Lublin
2009-03-04 18:15     ` Ryan Harper
2009-03-04 18:59       ` sudhir kumar
2009-03-04 22:23         ` Dor Laor
2009-03-09 16:23     ` Ryan Harper
2009-03-09 17:53       ` Uri Lublin

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=20090311205822.GX11777@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@redhat.com \
    --cc=uril@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox