You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
This commit c97d1b0 should fix this issue. Under the hood we will now still wait for that 200ms gap, but for a maximum time of 1 seconds, after which we will continue the execution normally.
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.
The text was updated successfully, but these errors were encountered: