From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31514 invoked by alias); 25 Sep 2007 18:10:47 -0000 Received: (qmail 31502 invoked by uid 22791); 25 Sep 2007 18:10:45 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Sep 2007 18:10:42 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8PIAeh4016907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Sep 2007 14:10:40 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8PIAeCi000626; Tue, 25 Sep 2007 14:10:40 -0400 Received: from tortoise.toronto.redhat.com (tortoise.toronto.redhat.com [172.16.14.92]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l8PIAdMe013288; Tue, 25 Sep 2007 14:10:39 -0400 Message-ID: <46F94F1F.8000103@redhat.com> Date: Tue, 25 Sep 2007 18:10:00 -0000 From: Thomas Fitzsimmons User-Agent: Thunderbird 2.0.0.5 (X11/20070719) MIME-Version: 1.0 To: =?UTF-8?B?U3RldmUgTWNLYXnimIQ=?= CC: mauve-discuss@sources.redhat.com Subject: Re: Tweaking default java.awt.Robot settings References: <4f2ee4520709241331o1a77379cudffb314dc1622914@mail.gmail.com> In-Reply-To: <4f2ee4520709241331o1a77379cudffb314dc1622914@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00026.txt.bz2 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? No objections here, that sounds like a good idea. When you say "significantly reduces failures", does that mean some non-deterministic failures persist with the new auto* settings? Tom