-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings when running a GUI testcase #274
Comments
Have the same problem, but I don't think that this is a matter of increasing timer limits. Problem occured after switching from JDK 11 to JDK 17 and has a stacktrace which shows an access to a module inside java.util
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run a Swing test, I get during the test run the following messages:
...
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
jul. 18,2023 08:12 WARNING Exception thrown by a TimerTask org.assertj.swing.monitor.ProtectingTimerTask ; handleException
...
Which timer can I increase to limit the messages?
And how do I do it?
The text was updated successfully, but these errors were encountered: