-
Bug
-
Resolution: Fixed
-
P4
-
jfx11, 9, 10
In order to increase the robustness of tests, including the ability to run on a wider array of systems, we should increase the timeout values used in various test.
In particular, the following should be evaluated and increased where it makes sense to do so:
1. Util.TIMEOUT -- currently set to 5 seconds, this should be increased to 10 seconds
This value is used both for tests that launch the FX runtime (using Application::lauch or Platform::startup) and as the timeout for the runnables passed to Util::runAndWait
2. Individual test timeout values -- this varies, but any test with a timeout value < 15 seconds should increase it to 15 seconds:
@Test(timeout=15000)
There are related concerns regarding individual sleep values, as tracked by JDK-8176884 and (maybe)JDK-8196614, but those are beyond the scope of this bug.
In particular, the following should be evaluated and increased where it makes sense to do so:
1. Util.TIMEOUT -- currently set to 5 seconds, this should be increased to 10 seconds
This value is used both for tests that launch the FX runtime (using Application::lauch or Platform::startup) and as the timeout for the runnables passed to Util::runAndWait
2. Individual test timeout values -- this varies, but any test with a timeout value < 15 seconds should increase it to 15 seconds:
@Test(timeout=15000)
There are related concerns regarding individual sleep values, as tracked by JDK-8176884 and (maybe)
- relates to
-
JDK-8269300 Some system tests use timeout values which are too small
-
- Open
-