-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DaaLoadTest MathLoadTest MiniMix crash vmState=0x000514ff vmState=0x000509ff #19947
Comments
@hzongaro can someone take a look at this with priority pls. It seems it may be responsible for taking AIX machines offline due to the amount of output. There is 800MB of console output from the backtraces, which I assume is blocking capturing any core file. |
Issue eclipse-openj9/openj9#19947 Signed-off-by: Peter Shipton <[email protected]>
See #19947 (comment) |
Also on zlinux https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/178/
17:48:17 MiniMix_3h_0 https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_1/178/ https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_special.system_s390x_linux_Personal_testList_3/122 |
For the time being I'm disabling the special.system test runs on AIX and zlinux. I've also added back x86_mac, aarch64_mac and xlinux, which were previously disabled due to infra problems. |
@midronij, is it possible this is related to your recent changes from pull request #17969? Looking at the jitdump from https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/178/system_test_output.tar.gz, it looks like the crash is happening while processing a call to |
https://openj9-jenkins.osuosl.org/job/Test_openjdk23_j9_sanity.openjdk_x86-64_linux_Nightly_testList_0/25/
|
The tests aren't really excluded, but I've set |
Although the open testing is limited, the tests are failing on all platforms except for aarch64. |
Reverted the suspected change causing the problem. |
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
A crash was occuring in Unsafe.get/put() case (6) when trying to modify the CFG to include the newly generated directAccessBlock. To avoid this, we can simply append the directAccessTreeTop onto the previous block (beforeCallBlock), which elimiates the need to update the CFG, since no new blocks are added. Additionally, without this commit, these two blocks (in addition to the one after the directAccessBlock, joinBlock), would get merged during block simplication anyways: so this fix eliminates the need to perform that optimization later down the line. Signed-off-by: midronij <[email protected]>
Related to https://github.ibm.com/runtimes/infrastructure/issues/9201
vmState [0x514ff]: {J9VMSTATE_JIT} {globalValuePropagation}
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_ppc64_aix_Personal_testList_1/133/
DaaLoadTest_daa1_special_5m_11 Mode351
-Xgcpolicy:metronome -Xcompressedrefs
vmState [0x509ff]: {J9VMSTATE_JIT} {localValuePropagation}
DaaLoadTest_daa2_special_5m_11
There are more failures on AIX, all versions. They are hard to look at since the output is so big.
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_special.system_ppc64_aix_Personal/122/
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_ppc64_aix_Personal/148/
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_ppc64_aix_Personal/133/
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_special.system_ppc64_aix_Personal/48/
The text was updated successfully, but these errors were encountered: