The following two tests fail in the Valhalla CI:
vmTestbase/nsk/jdi/BScenarios/multithrd/tc04x001/TestDescription.java
vmTestbase/nsk/jdi/Scenarios/invokeMethod/popframes001/TestDescription.java
Both tests are failing with "out of wait time" after completing successfully.
Here's a snippet from the BScenarios/multithrd/tc04x001 log file:
[13:30:31.170] debugee.stdout> [13:30:31.20] Thread-3::bar is called
[13:30:31.242] debugee.stdout> [13:30:31.179] Thread-2::bar is called
[13:30:31.305] debugee.stdout> [13:30:31.250] Thread-1::bar is called
[13:30:31.467] debugee.stdout> [13:30:31.412] Thread-1 finished
[13:30:31.547] debugee.stdout> [13:30:31.488] Thread-2 finished
[13:30:31.622] debugee.stdout> [13:30:31.567] Thread-3 finished
[13:30:31.681] debugee.stdout> [13:30:31.628] completed succesfully.
[13:34:15.492] # ERROR: debugger FAILURE> out of wait time...
The following stacktrace is for failure analysis.
nsk.share.TestFailure: debugger FAILURE> out of wait time...
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:309)
at nsk.share.Log.complain(Log.java:280)
at nsk.jdi.BScenarios.multithrd.tc04x001.complain(tc04x001.java:81)
at nsk.jdi.BScenarios.multithrd.tc04x001.execTest(tc04x001.java:186)
at nsk.jdi.BScenarios.multithrd.tc04x001.run(tc04x001.java:106)
at nsk.jdi.BScenarios.multithrd.tc04x001.main(tc04x001.java:85)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
[13:34:15.507] =============
[13:34:15.507] TEST FINISHES
[13:35:13.971] Test finished. exitStatus = 2
----------System.err:(10/556)----------
java.lang.RuntimeException: TEST FAILED with result 2
at nsk.jdi.BScenarios.multithrd.tc04x001.main(tc04x001.java:87)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED with result 2
Here's a snippet from the Scenarios/invokeMethod/popframes001 log file:
resuming...
[14:14:42.750]
event ===>>> MethodExitEvent@nsk.jdi.Scenarios.invokeMethod.popframes001b:70 in thread main
[14:14:42.750] MethodExitEvent:: method name : runIt
[14:14:42.751] MethodExitEvent:: is it <clinit>: false
[14:14:42.751] MethodExitEvent:: no actions for this method
[14:14:42.751]
resuming...
[14:14:42.755]
event ===>>> MethodExitEvent@nsk.jdi.Scenarios.invokeMethod.popframes001b:77 in thread main
[14:14:42.756] MethodExitEvent:: method name : runItCaller
[14:14:42.757] MethodExitEvent:: is it <clinit>: false
[14:14:42.757] MethodExitEvent:: no actions for this method
[14:14:42.757]
resuming...
[14:14:42.761] setting <finishIt> field
[14:15:7.563] debugee.stdout> [14:14:42.808] completed succesfully.
[14:20:0.879] # ERROR: out of wait time...
The following stacktrace is for failure analysis.
nsk.share.TestFailure: out of wait time...
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:309)
at nsk.share.Log.complain(Log.java:280)
at nsk.jdi.Scenarios.invokeMethod.popframes001.complain(popframes001.java:83)
at nsk.jdi.Scenarios.invokeMethod.popframes001.execTest(popframes001.java:207)
at nsk.jdi.Scenarios.invokeMethod.popframes001.run(popframes001.java:109)
at nsk.jdi.Scenarios.invokeMethod.popframes001.main(popframes001.java:87)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
[14:20:0.893] =============
[14:20:0.893] TEST FINISHES
[14:24:8.689] Test finished. exitStatus = 2
----------System.err:(10/566)----------
java.lang.RuntimeException: TEST FAILED with result 2
at nsk.jdi.Scenarios.invokeMethod.popframes001.main(popframes001.java:89)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED with result 2
There are currently 35 of the BScenarios/multithrd/tc04x001
failures in the Valhalla CI and all are on windows-x64.
There are currently 93 of the Scenarios/invokeMethod/popframes001
failures in the Valhalla CI and all are on windows-x64.
vmTestbase/nsk/jdi/BScenarios/multithrd/tc04x001/TestDescription.java
vmTestbase/nsk/jdi/Scenarios/invokeMethod/popframes001/TestDescription.java
Both tests are failing with "out of wait time" after completing successfully.
Here's a snippet from the BScenarios/multithrd/tc04x001 log file:
[13:30:31.170] debugee.stdout> [13:30:31.20] Thread-3::bar is called
[13:30:31.242] debugee.stdout> [13:30:31.179] Thread-2::bar is called
[13:30:31.305] debugee.stdout> [13:30:31.250] Thread-1::bar is called
[13:30:31.467] debugee.stdout> [13:30:31.412] Thread-1 finished
[13:30:31.547] debugee.stdout> [13:30:31.488] Thread-2 finished
[13:30:31.622] debugee.stdout> [13:30:31.567] Thread-3 finished
[13:30:31.681] debugee.stdout> [13:30:31.628] completed succesfully.
[13:34:15.492] # ERROR: debugger FAILURE> out of wait time...
The following stacktrace is for failure analysis.
nsk.share.TestFailure: debugger FAILURE> out of wait time...
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:309)
at nsk.share.Log.complain(Log.java:280)
at nsk.jdi.BScenarios.multithrd.tc04x001.complain(tc04x001.java:81)
at nsk.jdi.BScenarios.multithrd.tc04x001.execTest(tc04x001.java:186)
at nsk.jdi.BScenarios.multithrd.tc04x001.run(tc04x001.java:106)
at nsk.jdi.BScenarios.multithrd.tc04x001.main(tc04x001.java:85)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
[13:34:15.507] =============
[13:34:15.507] TEST FINISHES
[13:35:13.971] Test finished. exitStatus = 2
----------System.err:(10/556)----------
java.lang.RuntimeException: TEST FAILED with result 2
at nsk.jdi.BScenarios.multithrd.tc04x001.main(tc04x001.java:87)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED with result 2
Here's a snippet from the Scenarios/invokeMethod/popframes001 log file:
resuming...
[14:14:42.750]
event ===>>> MethodExitEvent@nsk.jdi.Scenarios.invokeMethod.popframes001b:70 in thread main
[14:14:42.750] MethodExitEvent:: method name : runIt
[14:14:42.751] MethodExitEvent:: is it <clinit>: false
[14:14:42.751] MethodExitEvent:: no actions for this method
[14:14:42.751]
resuming...
[14:14:42.755]
event ===>>> MethodExitEvent@nsk.jdi.Scenarios.invokeMethod.popframes001b:77 in thread main
[14:14:42.756] MethodExitEvent:: method name : runItCaller
[14:14:42.757] MethodExitEvent:: is it <clinit>: false
[14:14:42.757] MethodExitEvent:: no actions for this method
[14:14:42.757]
resuming...
[14:14:42.761] setting <finishIt> field
[14:15:7.563] debugee.stdout> [14:14:42.808] completed succesfully.
[14:20:0.879] # ERROR: out of wait time...
The following stacktrace is for failure analysis.
nsk.share.TestFailure: out of wait time...
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:309)
at nsk.share.Log.complain(Log.java:280)
at nsk.jdi.Scenarios.invokeMethod.popframes001.complain(popframes001.java:83)
at nsk.jdi.Scenarios.invokeMethod.popframes001.execTest(popframes001.java:207)
at nsk.jdi.Scenarios.invokeMethod.popframes001.run(popframes001.java:109)
at nsk.jdi.Scenarios.invokeMethod.popframes001.main(popframes001.java:87)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
[14:20:0.893] =============
[14:20:0.893] TEST FINISHES
[14:24:8.689] Test finished. exitStatus = 2
----------System.err:(10/566)----------
java.lang.RuntimeException: TEST FAILED with result 2
at nsk.jdi.Scenarios.invokeMethod.popframes001.main(popframes001.java:89)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED with result 2
There are currently 35 of the BScenarios/multithrd/tc04x001
failures in the Valhalla CI and all are on windows-x64.
There are currently 93 of the Scenarios/invokeMethod/popframes001
failures in the Valhalla CI and all are on windows-x64.
There are no Sub-Tasks for this issue.