From: David Herron <David.Herron@Sun.COM>
To: "Steve McKay☄" <smckay@google.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Tweaking default java.awt.Robot settings
Date: Mon, 24 Sep 2007 20:50:00 -0000 [thread overview]
Message-ID: <46F8238C.8020606@sun.com> (raw)
In-Reply-To: <4f2ee4520709241331o1a77379cudffb314dc1622914@mail.gmail.com>
Steve McKayâ wrote:
> Hi All,
>
> I've noticed that at least some of the tests using java.awt.Robot are
> non-deterministic due to lags is the underlying window system. The
> java.awt.Component.keyPressTest, for example, fails some of the time
> (on linux, windows, linux+wine, ...). It looks like enabling
> autoWaitForIdle (waits for the awt EventQueue to be empty before
> adding new events to the queue), and setting autoDelay (pauses for an
> arbitrary period of time) to some magic number of millis well above
> zero (I use 100) significantly reduces failures. Would anyone object
> to configuring the Robot with settings like this by default? If no,
> should the config mechanism be updated to allow tweaking these
> settings?
>
>
I don't know what the classpath implementation of Robot looks like, but
I do know what Sun's Linux/Unix implementation looks like (having
written the original version).
Generally Robot has to request the OS or X11 to synthesize the event.
On Windows there's a direct API call, while on Unix/Linux there is a
child process which ends up calling XTEST extension methods. In both
cases it means there is a nondeterministic delay due to the current
process scheduling characteristics of the given system. In other words
it depends on an external entity, who Robot cannot coerce into
performing the request within a bounded set of time.
I think that means depending on Robot doing it's thing within a given
period of time is an invalid test.
Robot does not add events to EventQueue but it requests the OS to
synthesize an OS-level event.
- David Herron
next prev parent reply other threads:[~2007-09-24 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:31 Steve McKay☄
2007-09-24 20:50 ` David Herron [this message]
2007-09-24 21:22 ` Steve McKay☄
2007-09-24 21:41 ` David Herron
2007-09-25 18:33 ` Lillian Angel
2007-09-25 19:13 ` Steve McKay☄
2007-09-25 19:27 ` Lillian Angel
2007-09-25 19:37 ` Steve McKay☄
2007-09-25 19:45 ` Lillian Angel
2007-09-25 19:27 ` David Herron
2007-09-25 18:33 ` Thomas Fitzsimmons
2007-09-25 18:57 ` Steve McKay☄
2007-09-25 19:58 ` Thomas Fitzsimmons
2007-09-25 20:28 ` Steve McKay☄
2007-10-04 0:43 ` Steve McKay☄
2007-10-04 13:04 ` Lillian Angel
2007-09-25 19:24 ` David Herron
2007-09-25 18:10 ` Thomas Fitzsimmons
2007-09-25 18:14 ` Steve McKay☄
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=46F8238C.8020606@sun.com \
--to=david.herron@sun.com \
--cc=mauve-discuss@sources.redhat.com \
--cc=smckay@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).