Amarpreet Singh

I was able to generate a [core file](https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/39087/execution/node/11/ws/aqa-tests/TKG/output_17111297634281/CpMpJlink_0_ITER_213/20240322-115515-CpMpJlinkTest/results/) for `ClassCastException: jdk.internal.classfile.impl.BoundAttribute$BoundAnnotationDefaultAttr incompatible with java.lang.classfile.CodeModel` in a [grinder](https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/39087/) which utilized a [jdk that enables -Xdump by default](https://github.com/singh264/openj9/commit/a9dcf8458f67ec1ab85f524d28cba04e208f7ba9). The core file indicates...

@hzongaro I would like your input for addressing this issue. The [core files](https://na.artifactory.swg-devops.com/ui/native/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/Grinder/39087/) that were generated in a [grinder](https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/39087/) due to a `ClassCastException` indicates a potential jit issue, where the...

@hzongaro how can I know the status of the issue?

@a7ehuo how can I request a grinder that runs [CpMpJlinkTest](https://github.com/adoptium/aqa-systemtest/blob/00de74587e5ac2849df0409a00699f21e39c824d/openjdk.test.modularity/src/com.stf/net/adoptopenjdk/test/modularity/CpMpJlinkTest.java) for 1000 iterations on a ppc64le linux machine to confirm the analysis of the collected logs?

It seems like the next step is to start a grinder that runs [CpMpJlinkTest](https://github.com/adoptium/aqa-systemtest/blob/00de74587e5ac2849df0409a00699f21e39c824d/openjdk.test.modularity/src/com.stf/net/adoptopenjdk/test/modularity/CpMpJlinkTest.java) for 1000 iterations on a ppc64le linux machine to confirm the analysis of the collected logs.

@tajila requesting your review.

@ChengJin01 re-requesting your review.

@tajila re-requesting your review.

@tajila how can the [JLM_Tests build fail](https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_ppc64le_linux_Personal_testList_0/66/console) in jenkins despite it passing locally on a `x86-64 linux` machine? Local build: ``` // make compile (in TKG) ... build: init: ......

> This is because CRAC_SUPPORT is only enabled by default at Linux x64 platform. Would it be incorrect to enable `CRAC_SUPPORT` by default on `x86-64 linux`, `ppc64le linux`, `aarch64 linux`...