-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Update JDK18 test exclude list #3211
Conversation
Reviewers: @llxia @Mesbah-Alam |
In eclipse-openj9/openj9#14079 (comment), I had a question for the test team:
This PR will close eclipse-openj9/openj9#14079. Requesting test team to respond to this question in eclipse-openj9/openj9#14079 before merging this PR. |
Not sure eclipse-openj9/openj9#14079 is a duplicate of adoptium/temurin-build#248. Raising the question at eclipse-openj9/openj9#14079 (comment) |
a1ac005
to
31e5bbb
Compare
I have updated the PR. eclipse-openj9/openj9#14079 is no longer treated as a duplicate of adoptium/temurin-build#24. As per eclipse-openj9/openj9#14079 (comment), all tests disabled for adoptium/temurin-build#248 have been re-enabled. fyi @llxia @sophia-guo. |
Thanks @babsingh for reenabling all tests that are excluded due to 248. However, IMHO, it may be better to enable these tests step by step after proper testing (in a separate issue/PR #3214) as these tests have been excluded for a long time for both openj9 and hotspot (some of them have been excluded since JDK10) and we are going to have a release soon. FYI @smlambert |
- eclipse-openj9/openj9#14091 is a duplicate of adoptium#1297. - eclipse-openj9/openj9#14095 is a duplicate of eclipse-openj9/openj9#11930. - Individual sub-tests of StringBuilder/HugeCapacity are excluded. Closes: eclipse-openj9/openj9#14091 Closes: eclipse-openj9/openj9#14095 Signed-off-by: Babneet Singh <[email protected]>
Fixed by ibmruntimes/openj9-openjdk-jdk18#4. Also, adoptium/temurin-build#248 has been closed. Now, exeCallerAccessTest/CallerAccessTest passes with OpenJ9 JDK18. Signed-off-by: Babneet Singh <[email protected]>
re #3211 (comment): You are correct. Yesterday, I ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @babsingh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Excluding StringBuilder/HugeCapacity sub-tests does not work. So, the StringBuilder/HugeCapacity changes in #3211 have been reverted. The original StringBuilder/HugeCapacity exclude change has been re-added. Signed-off-by: Babneet Singh <[email protected]>
Commit 1: [JDK18] Remove duplicates and exclude sub-tests
-- eclipse-openj9/openj9#14091 is a duplicate of #1297.
-- eclipse-openj9/openj9#14095 is a duplicate of eclipse-openj9/openj9#11930.
-- Individual sub-tests of
StringBuilder/HugeCapacity
are excluded.Closes: eclipse-openj9/openj9#14091
Closes: eclipse-openj9/openj9#14095
Commit 2: [JDK18] Re-enable exeCallerAccessTest/CallerAccessTest
Fixed by ibmruntimes/openj9-openjdk-jdk18#4.
Also, adoptium/temurin-build#248 has been closed.
Now,
exeCallerAccessTest/CallerAccessTest
passes with OpenJ9 JDK18.Signed-off-by: Babneet Singh [email protected]