jcmd test cases in jdk_tools FAILED on test-docker-ubuntu2204-ppc64le-1 and test-docker-debian11-ppc64le-1

[smlambert]

Appears to be an extra character on the end of the jcmd options when running some jcmd tests from jdk_tools target on test-docker-ubuntu2204-ppc64le-1 and test-docker-debian11-ppc64le-1.

sun/tools/jcmd/TestJcmdDefaults.java

[/home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1/openjdkbinary/j2sdk-image/bin/jcmd -J-XX:+UsePerfData -h]
Usage: jcmd <pid | main class> <command ...|PerfCounter.print|-f file>
   or: jcmd -l                                                    
   or: jcmd -h          

and

sun/tools/jcmd/TestJcmdSanity.java

[/home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1/openjdkbinary/j2sdk-image/bin/jcmd -J-XX:+UsePerfData 294202 help]
294202:
The following commands are available:
VM.unlock_commercial_features
JFR.configure
JFR.stop
JFR.start
JFR.dump
JFR.check
...

• test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)?
• a link into recent Test_ job on https://ci.adoptopenjdk.net which showed the failure https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1/86
• Hyperlink to re-run in Grinder: Rerun in Grinder
• Is there an existing issue elsewhere covering this? No
• Which machine(s) does it work on? test-osuosl-ubuntu1604-ppc64le-1, test-osuosl-ubuntu1604-ppc64le-2, test-osuosl-ubuntu1804-ppc64le-2
• Which machine(s) does it fail on? test-docker-ubuntu2204-ppc64le-1 and test-docker-debian11-ppc64le-1

---

Test Info
Test Name: jdk_tools_0
Test Duration: 16 min 43 sec
Machine: test-docker-ubuntu2204-ppc64le-1
TRSS link for the test output: https://trss.adoptium.net/output/test?id=63c21fffed0b30773ba35f54

Build Info
Build Name: Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1
Jenkins Build start time: Jan 13 2023, 06:19 pm
Jenkins Build URL: https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1/86/
TRSS link for the build: https://trss.adoptium.net/allTestsInfo?buildId=63c21f23ed0b30773ba35d15

Java Version
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_362-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.362-b06, mixed mode)

This test has been failed 2 times since Jan 12 2023, 09:56 am
Java Version when the issue first seen
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_362-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.362-b06, mixed mode)
Jenkins Build URL: https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_ppc64le_linux_testList_1/85/

The test failed on machine test-docker-ubuntu2204-ppc64le-1 1 times
The test failed on machine test-docker-debian11-ppc64le-1 1 times

[Haroon-Khel]

Rerunning on problem machines, and others that I suspect will have the same problem
test-docker-ubuntu2204-ppc64le-1 https://ci.adoptopenjdk.net/job/Grinder/6351/console
test-docker-ubuntu2204-ppc64le-2 https://ci.adoptopenjdk.net/job/Grinder/6352/console
test-docker-debian11-ppc64le-1 https://ci.adoptopenjdk.net/job/Grinder/6353/console
test-docker-debian11-ppc64le-2 https://ci.adoptopenjdk.net/job/Grinder/6354/console
test-docker-debian11-ppc64le-3 https://ci.adoptopenjdk.net/job/Grinder/6355/console

[Haroon-Khel]

Multiple failures on all but debian11-3. A bit confusing as they were set up at the same time and are all on the same dockerhost machine

com/sun/tools/attach/BasicTests.java.BasicTests
com/sun/tools/attach/TempDirTest.java.TempDirTest
sun/jvmstat/monitor/MonitoredVm/CR6672135.java.CR6672135
sun/jvmstat/monitor/MonitoredVm/MonitorVmStartTerminate.java.MonitorVmStartTerminate
sun/tools/jcmd/TestJcmdDefaults.java.TestJcmdDefaults
sun/tools/jcmd/TestJcmdSanity.java.TestJcmdSanity
sun/tools/jps/TestJpsClass.java.TestJpsClass
sun/tools/jps/TestJpsJar.java.TestJpsJar

I'll keep the problem machines offline. Theres plenty of other ppc64le linux test machines

[Haroon-Khel]

Created a new debian ppc64le node on the same dockerhost of the problem machines (with the same docker image of that of the problem machines), https://ci.adoptium.net/computer/test-docker-debian11-ppc64le-4/
The jdk_tools suite passes fine on this new node
https://ci.adoptium.net/view/Test_grinder/job/Grinder/6746/

[Haroon-Khel]

I am closing this as I have replaced the problem container with a working one. The failing container is offline in jenkins and is to be decommissioned