Details
-
Bug
-
Resolution: Fixed
-
P4
-
None
-
None
-
b23
Description
In passing runs of the test test/jdk/javax/management/monitor/ThreadPoolAccTest.java, it is common to see over 1500 lines of, e.g.:
Task not submitted Thu Oct 26 14:26:12 UTC 2023. RETRY
...with a truncation warning in the middle (i.e. there was more!):
...
Output overflow:
JT Harness has limited the test output to the text
at the beginning and the end, so that you can see how the
test began, and how it completed.
If you need to see more of the output from the test,
set the system property javatest.maxOutputSize to a higher
value. The current value is 100000
...
In a genuine failure, missing log lines mean it's hard to be confident what happened. The test should back off or sleep, not log this message as fast as it can until stopped.
The testPrincipals method makes no distinction between a principal being not there yet, and never being there. It retries on null, continually until timeout. It should try a reasonable number of times, then fail.
Task not submitted Thu Oct 26 14:26:12 UTC 2023. RETRY
...with a truncation warning in the middle (i.e. there was more!):
...
Output overflow:
JT Harness has limited the test output to the text
at the beginning and the end, so that you can see how the
test began, and how it completed.
If you need to see more of the output from the test,
set the system property javatest.maxOutputSize to a higher
value. The current value is 100000
...
In a genuine failure, missing log lines mean it's hard to be confident what happened. The test should back off or sleep, not log this message as fast as it can until stopped.
The testPrincipals method makes no distinction between a principal being not there yet, and never being there. It retries on null, continually until timeout. It should try a reasonable number of times, then fail.
