Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8240139

JVMTI TC05/tc05t001 still fails on Win* after JDK-8227563

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 11-pool, 15, 16, 17, 18, 21
    • hotspot
    • x86_64
    • windows

      The following test failed in the JDK15 CI:

      vmTestbase/nsk/jvmti/scenarios/contention/TC05/tc05t001/TestDescription.java

      Here's a snippet from the log file:

      #section:main
      ----------messages:(4/305)----------
      command: main -agentlib:tc05t001=verbose,waittime=5 nsk.jvmti.scenarios.contention.TC05.tc05t001
      reason: User specified action: run main/othervm/native -agentlib:tc05t001=verbose,waittime=5 nsk.jvmti.scenarios.contention.TC05.tc05t001
      Mode: othervm [/othervm specified]
      elapsed time (seconds): 1.234
      ----------configuration:(0/0)----------
      ----------System.out:(30/1972)----------
      - tc05t001.cpp, 322: Timeout: 300000 msc
      - tc05t001.cpp, 149: Prepare: find tested thread
      - tc05t001.cpp, 167: thread #0 (main): 0000004B82A26D48
      - tc05t001.cpp, 167: thread #1 (Reference Handler): 0000004B82A26D50
      - tc05t001.cpp, 167: thread #2 (Finalizer): 0000004B82A26D58
      - tc05t001.cpp, 167: thread #3 (Signal Dispatcher): 0000004B82A26D60
      - tc05t001.cpp, 167: thread #4 (Attach Listener): 0000004B82A26D68
      - tc05t001.cpp, 167: thread #5 (Notification Thread): 0000004B82A26D70
      - tc05t001.cpp, 167: thread #6 (Common-Cleaner): 0000004B82A26D78
      - tc05t001.cpp, 167: thread #7 (MainThread): 0000004B82A26D80
      - tc05t001.cpp, 167: thread #8 (Debuggee Thread): 0000004B82A26D88
      - tc05t001.cpp, 167: thread #9 (JVMTI agent thread): 0000004B82A26D90
      - tc05t001.cpp, 88: MonitorWait event:
      - tc05t001.cpp, 90: thread: 0000004B82A26EC8, object: 0000004B82A26ED0, timeout: 1
      - tc05t001.cpp, 92: time: 6652760525777840
      - tc05t001.cpp, 94: thread CPU time: 0
      - tc05t001.cpp, 127: MonitorWaited event:
      - tc05t001.cpp, 129: thread: 0000004B82A26EC8, object: 0000004B82A26ED0, timed_out: true
      - tc05t001.cpp, 131: GetTime: 6652760593184950
      - tc05t001.cpp, 133: thread CPU time: 31250000
      - tc05t001.cpp, 257: Number of MonitorWait events: 1
      - tc05t001.cpp, 262: Number of MonitorWaited events: 1
      - tc05t001.cpp, 268: Time frame between the events: 67407110 ns
      - tc05t001.cpp, 280: Thread CPU time between the events: 31250000 ns
      The following fake exception stacktrace is for failure analysis.
      nsk.share.Fake_Exception_for_RULE_Creation: (tc05t001.cpp:282) (waitedThreadCpuTime - waitThreadCpuTime) < (EXPECTED_ACCURACY * 1000000)
      at nsk_lvcomplain(nsk_tools.cpp:172)
      # ERROR: tc05t001.cpp, 282: (waitedThreadCpuTime - waitThreadCpuTime) < (EXPECTED_ACCURACY * 1000000)
      # verified assertion is FALSE
      waitedThreadCpuTime: 31250000, waitThreadCpuTime: 0, waitedThreadCpuTime - waitThreadCpuTime: 31250000
      ----------System.err:(3/175)----------
      java version "15-ea" 2020-09-15
      Java(TM) SE Runtime Environment (fastdebug build 15-ea+12-428)
      Java HotSpot(TM) 64-Bit Server VM (fastdebug build 15-ea+12-428, mixed mode)
      ----------rerun:(40/5882)*----------

            Unassigned Unassigned
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: