Several places in SwingLibrary use Jemmy's EventTool.waitNoEvent with time of 200ms. This waits until there is a gap of 200ms during which there are no new events to event queue. The operation timeouts at 3 minutes (!) and fails the keyword call if that happens.
Now if the SUT generates new events for example every 100ms, this of course causes the test to hang for 3 minutes and then to fail.
Several places in SwingLibrary use Jemmy's EventTool.waitNoEvent with time of 200ms. This waits until there is a gap of 200ms during which there are no new events to event queue. The operation timeouts at 3 minutes (!) and fails the keyword call if that happens.
Now if the SUT generates new events for example every 100ms, this of course causes the test to hang for 3 minutes and then to fail.