You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
20:46:23 NativeTestHelper::DEFAULT_RANDOM.seed = -934734214
20:46:23 Re-run with '-DNativeTestHelper.DEFAULT_RANDOM.seed=-934734214' to reproduce
20:46:23 test TestCritical.testAllowHeap(TestCritical$AllowHeapCase@c1a75416): failure
20:46:23 java.lang.AssertionError: expected [42] but found [0]
20:46:23 at org.testng.Assert.fail(Assert.java:99)
20:46:23 at org.testng.Assert.failNotEquals(Assert.java:1037)
20:46:23 at org.testng.Assert.assertEqualsImpl(Assert.java:140)
20:46:23 at org.testng.Assert.assertEquals(Assert.java:122)
20:46:23 at org.testng.Assert.assertEquals(Assert.java:907)
20:46:23 at org.testng.Assert.assertEquals(Assert.java:917)
20:46:23 at TestCritical.testAllowHeap(TestCritical.java:141)
The text was updated successfully, but these errors were encountered:
@theresa-m Can you please take a look at this issue?
There is a recent commit in the JDK24 extension repo where TestCritical testAllowHeap is modified: 8336768: Allow captureCallState and critical linker options to be combined. There might be API changes that we need to reflect in our implementation. To begin the investigation, we should run the test with RI's latest JDK24 early-access build to see if it passes the test.
I confirmed that this is passing with an OpenJDK build. I will take a look at the recent extensions change to see if I can find anything that's missing from OpenJ9.
https://openj9-jenkins.osuosl.org/job/Test_openjdk24_j9_sanity.openjdk_aarch64_mac_Nightly_testList_1/3
java/foreign/critical/TestCritical.java
The text was updated successfully, but these errors were encountered: