-
Bug
-
Resolution: Incomplete
-
P4
-
None
-
9
java/util/logging/LoggingDeadlock.java timeouts in 2016-04-20 hs nightly on win64 platform.
From .jtr log I see that test passed, but then for some reasons it hangs:
----------messages:(6/242)----------
command: main LoggingDeadlock
reason: User specified action: run main/timeout=15 LoggingDeadlock
Timeout information:
Could not find process id for the process that timed out.
Skipping timeout handling.
elapsed time (seconds): 240.018
----------System.out:(3/52)----------
Test passed
Timeout signalled after 240 seconds
----------System.err:(1/16)----------
STATUS:Passed.
Options: -server -Xmixed -XX:MaxRAMFraction=8 -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops
Unfortunately, timeout handler was failed.
From .jtr log I see that test passed, but then for some reasons it hangs:
----------messages:(6/242)----------
command: main LoggingDeadlock
reason: User specified action: run main/timeout=15 LoggingDeadlock
Timeout information:
Could not find process id for the process that timed out.
Skipping timeout handling.
elapsed time (seconds): 240.018
----------System.out:(3/52)----------
Test passed
Timeout signalled after 240 seconds
----------System.err:(1/16)----------
STATUS:Passed.
Options: -server -Xmixed -XX:MaxRAMFraction=8 -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops
Unfortunately, timeout handler was failed.