JDK-8221433 : vmTestbase/gc/lock/jniref/jnireflock04/TestDescription.java timeout
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 13
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2019-03-25
  • Updated: 2019-04-25
  • Resolved: 2019-04-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 13
13Resolved
Related Reports
Duplicate :  
Description
----------System.out:(21/845)----------
Stress time: 30 seconds
Stress iterations factor: 1
Stress threads factor: 1
Stress runs factor: 1
Max memory: 2063597568
Sleep time: 500
Iterations: 0
Number of threads: 8
Seed: 1550752840112
Run GC thread: false
Run mem diag thread: false
Run forever: false
Starting Thread[gc.lock.LockerTest$Worker@7a473b5,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@6fdb47bb,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@4bc6b82e,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@17f5ad46,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@28481a70,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@1d9b765d,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@6362aa08,5,MainThreadGroup]
Starting Thread[gc.lock.LockerTest$Worker@59c7a4bf,5,MainThreadGroup]
Timeout refired 480 times
Comments
All the failures with Graal are consistent with JDK-8218700. It would be nice if the jtreg timeout handler would send a SIGQUIT so we could get a thread dump.
25-04-2019

We have 3 reported timeout failures for this so far. One seems an unrelated crash in a personal build. The other two are on macosx. Of those, one is well before the fix for JDK-8218975, so might be that. The most recent one is shortly after that fix was made, and it's been verified to include that fix.
27-03-2019