openj9 icon indicating copy to clipboard operation
openj9 copied to clipboard

JDK11 jdmpview doesn't work on some OS version/machines

Open JasonFengJ9 opened this issue 3 years ago • 6 comments

Failure link

From an internal build(rhel9x86-rt2-1.fyre.ibm.com):

23:24:16  java version "11.0.16" 2022-07-19
23:24:16  IBM Semeru Runtime Certified Edition 11.0.16.0-rc1 (build 11.0.16+8)
23:24:16  Eclipse OpenJ9 VM 11.0.16.0-rc1 (build openj9-0.33.0-rc1, JRE 11 Linux amd64-64-Bit Compressed References 20220720_388 (JIT enabled, AOT enabled)
23:24:16  OpenJ9   - 8cb527940
23:24:16  OMR      - b58aa2708
23:24:16  JCL      - 8b2d4875e9 based on jdk-11.0.16+8)

Rerun in Grinder - Change TARGET to run only the failed test targets.

Optional info

Failure output (captured from console output)

Testing: Run !allclasses
Test start time: 2022/07/19 20:50:51 Pacific Standard Time
Running command: /home/jenkins/workspace/Test_openjdk11_j9_extended.functional_x86-64_linux_testList_1/openjdkbinary/j2sdk-image/bin/jdmpview -core j9core.dmp
Time spent starting: 3 milliseconds
Time spent executing: 6524 milliseconds
Test result: FAILED
 [OUT] DTFJView version 4.29.5, using DTFJ version 1.12.29003
 [OUT] Loading image from DTFJ...
 [OUT] 
 [OUT] Problem running command: 
 [OUT] null
 [OUT] For a list of commands, type "help"; for how to use "help", type "help help"
 [OUT] > DDR is not enabled for this core file, '!' commands are disabled
 [OUT] > 
>> Success condition was not found: [Output match: java/lang/Object]
>> Failure condition was not found: [Output match: DDRInteractiveCommandException]
>> Failure condition was not found: [Output match: unable to read]
>> Failure condition was not found: [Output match: could not read]
>> Failure condition was not found: [Output match: dump event]

---TEST RESULTS---
Number of PASSED tests: 3 out of 8
Number of FAILED tests: 5 out of 8

---SUMMARY OF FAILED TESTS---
Run !allclasses
Run !dumpallromclasslinear 10
Run !dumpallramclasslinear 10
Run !romclasssummary
Run !ramclasssummary
-----------------------------


cmdLineTester_classesdbgddrext_0_FAILED

The failure is consistent at this machine - grinder in same machine - all failed Login to the machine, the core generation was successful, but jdmpview failed to load/parse it.

grinder in 5 different machines passed four machines rhel7x64cudart1 cent7x64-1-10 ub18x64rt1-1 cent7x64-1-7 failed at ubu22x86-rt4-1

Related to an internal infra issue

JasonFengJ9 avatar Jul 27 '22 20:07 JasonFengJ9

I tried the build referenced in the description with the core file used in the failing !allclasses test on a Ubuntu 22.04 system: it passes. There must be something peculiar about ubu22x86-rt4-1: I'll try again there.

keithc-ca avatar Jul 28 '22 18:07 keithc-ca

The test passes on ubu22x86-rt4-1 as well.

keithc-ca avatar Jul 28 '22 18:07 keithc-ca

I expect this is another one of those problems where it doesn't work on the original machine with all the original libraries available, but works when you try it otherwise.

pshipton avatar Jul 28 '22 18:07 pshipton

Last time to recreate one of these I restored the original JVM to the expected place on the file system. Although there are command line options that may work as well if the JVM is in a different place.

pshipton avatar Jul 28 '22 19:07 pshipton

In my first test on ubuntu22, I ran the test in the same way as the build so everything was in the same place as when the core was created: that seems to discount that theory.

keithc-ca avatar Jul 28 '22 19:07 keithc-ca

Can we modify the test to get more logging about the failure when it does occur?

pshipton avatar Jul 28 '22 20:07 pshipton

I'm not seeing any problem running the test on ubu22x86-rt4-1 with the latest builds. I wonder if the problem was related to https://github.com/eclipse-openj9/openj9/pull/15734 which was added to the 0.33.1 release. I'll go ahead and close this until the problem is seen again.

pshipton avatar Aug 26 '22 13:08 pshipton