-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
There are several places in WFLY testsuite which use calls like Thread.sleep(...) or wait for some time elapses. Some of these calls do not consider that waiting time should be adapted based on the system property ts.timeout.factor.
This is for what is created a helper class in testsuite shared module TimeoutUtil (https://github.com/wildfly/wildfly-core/blob/12.0.1.Final/testsuite/shared/src/main/java/org/jboss/as/test/shared/TimeoutUtil.java).
Reason: we have a slower CI machine and we struggle with timeout issues from places which does not consider this configuration
- is related to
-
WFLY-14855 Make configurable timeout for test StopFromDifferentNodeTestCase
- Closed
-
WFLY-13824 Use TimeUtil timeout adjustments in cases of timeout defined on JMS receive
- Closed
-
WFLY-14828 Add timeout parametrization for multinode DatabaseTimerServiceMultiNodeTestCase
- Closed