-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 6
-
Component/s: client-libs
-
b83
-
generic
-
solaris_9
It is possible to run Java2Demo in auto mode by passing the -runs=N argument from
the command line. The mechanism that Java2Demo uses in its main() method to
kick off the RunWindow that drives the automation is flaky, and it seems that some
timing changes (perhaps in AWT or Swing) in Mustang cause this feature to not
work reliably. Sometimes the programmatic mouse click that kicks off
the RunWindow will miss its target since the RunWindow isn't yet visible, so
Java2Demo will run indefinitely as a result. This is clearly a problem in those
cases where we want to run Java2Demo without manual intervention for a short time
(e.g. -runs=1 -delay=5, as a quick reliability test for the OpenGL pipeline).
the command line. The mechanism that Java2Demo uses in its main() method to
kick off the RunWindow that drives the automation is flaky, and it seems that some
timing changes (perhaps in AWT or Swing) in Mustang cause this feature to not
work reliably. Sometimes the programmatic mouse click that kicks off
the RunWindow will miss its target since the RunWindow isn't yet visible, so
Java2Demo will run indefinitely as a result. This is clearly a problem in those
cases where we want to run Java2Demo without manual intervention for a short time
(e.g. -runs=1 -delay=5, as a quick reliability test for the OpenGL pipeline).