Skip to content
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

jdk24 OpenJDK java/foreign/passheapsegment/TestPassHeapSegment testNoHeapCaptureCallState should have thrown an exception of type class java.lang.IllegalArgumentException #21019

Closed
pshipton opened this issue Jan 25, 2025 · 3 comments · Fixed by adoptium/aqa-tests#5986

Comments

@pshipton
Copy link
Member

https://openj9-jenkins.osuosl.org/job/Test_openjdk24_j9_sanity.openjdk_aarch64_mac_Nightly_testList_1/3
java/foreign/passheapsegment/TestPassHeapSegment.java

20:46:31  test TestPassHeapSegment.testNoHeapCaptureCallState(): failure
20:46:31  org.testng.TestException: 
20:46:31  Method TestPassHeapSegment.testNoHeapCaptureCallState()[pri:0, instance:TestPassHeapSegment@634536a4] should have thrown an exception of type class java.lang.IllegalArgumentException
@pshipton
Copy link
Member Author

Exclude it via adoptium/aqa-tests#5912

llxia pushed a commit to adoptium/aqa-tests that referenced this issue Jan 26, 2025
@babsingh
Copy link
Contributor

babsingh commented Feb 4, 2025

@theresa-m Can you also please take a look at this issue?

This might be related to #21018 (comment). The same extension repo commit also modifies TestPassHeapSegment testNoHeapCaptureCallState: 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.

@pshipton
Copy link
Member Author

pshipton commented Mar 4, 2025

@theresa-m any updates? nm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants