-
Task
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
-
False
-
False
-
Undefined
-
When the TestUtils.waitFor(..) method fails on timeout, we just get simple info which is specified as a method parameter -> for example:
io.strimzi.test.WaitException: Timeout after 300000 ms waiting for Logger change
at io.strimzi.test.TestUtils.waitFor(TestUtils.java:136)
at io.strimzi.test.TestUtils.waitFor(TestUtils.java:117)
at io.strimzi.systemtest.log.LoggingChangeST.testDynamicallySetConnectLoggingLevels(LoggingChangeST.java:677)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
But, we should also print last result of the waitFor into the debug log - this will help us find out what's wrong.
So, the best way should be to add one more exec on timeout and then print everything to debug log.