-
Notifications
You must be signed in to change notification settings - Fork 721
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
JEP 393: Foreign-Memory Access API (Third Incubator) #11027
Comments
This has been assigned to @babsingh |
#11182 introduces the following two native stubs:
New tests and failures are seen for JEP393 (Foreign Memory Access API's Third Incubator):
More details about the failures can be found in the following log: jep393_tests_19Nov20.log. Need to implement |
More JEP393 failures: #11135 (comment). |
Note: following tests are excluded via adoptium/aqa-tests#2085
|
More excludes for
|
Do all the tests, which are being excluded, fail? As per the log file in #11027 (comment) (generated 2 weeks ago), few of these tests pass. |
Some of these tests are related to JEP389 rather than JEP393 |
JEP389 tests also run as part of the
|
Yes, all excluded tests still fail in internal tests. |
Will check and refer JEP 389 instead. |
We need to track them differently as there is a chance that JEP393 will be ready for 0.25 and JEP389 will not |
From an internal build
|
Locally, some of the |
Below is the updated list of JEP393 test failures after ibmruntimes/openj9-openjdk-jdk16#9 is merged for the 0.25 release:
The above tests fail because of
The above assertion failure is being tracked via this issue #11027 (comment) and #11360 (duplicate). |
JEP393 is targeted for JDK17 (0.28 release). |
They were excluded under eclipse-openj9/openj9#11027 but are not excluded from jdk19+. Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
They were excluded under eclipse-openj9/openj9#11027 but are not excluded from jdk19+. Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Un-exclude some of the tests excluded under this issue via adoptium/aqa-tests#4211 The remaining jdk17 excludes done via this issue are still excluded on jdk19 under the following (open) issues: #13999 #14002 - perm exclude #14134 plus #13993 which is a permanent exclude |
They were excluded under eclipse-openj9/openj9#11027 but are not excluded from jdk19+. Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
They were excluded under eclipse-openj9/openj9#11027 but are not excluded from jdk19+. Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com> Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
See https://openjdk.java.net/jeps/393
The text was updated successfully, but these errors were encountered: