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
IndexOutOfBoundsException was captured in VaListTest.testVaListMemorySegment() on zLinux as follows:
VaListTest$$Lambda$239/0x00000000c017bc68@b814d76c, a64): failure
java.lang.IndexOutOfBoundsException: Out of bound access on segment MemorySegment{ array: Optional.empty address:139847358506464 limit: 0 }; new offset = 0; new length = 4
at java.base/jdk.internal.foreign.AbstractMemorySegmentImpl.outOfBoundException(AbstractMemorySegmentImpl.java:371)
at java.base/jdk.internal.foreign.AbstractMemorySegmentImpl.apply(AbstractMemorySegmentImpl.java:357)
at java.base/jdk.internal.foreign.AbstractMemorySegmentImpl.apply(AbstractMemorySegmentImpl.java:70)
at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:98)
at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:124)
at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:448)
at java.base/jdk.internal.foreign.AbstractMemorySegmentImpl.checkBounds(AbstractMemorySegmentImpl.java:346)
at java.base/jdk.internal.foreign.AbstractMemorySegmentImpl.checkAccess(AbstractMemorySegmentImpl.java:311)
at java.base/java.lang.invoke.VarHandleSegmentAsInts.checkAddress(VarHandleSegmentAsInts.java:81)
at java.base/java.lang.invoke.VarHandleSegmentAsInts.get(VarHandleSegmentAsInts.java:108)
at java.base/java.lang.foreign.MemorySegment.get(MemorySegment.java:1552)
at VaListTest.lambda$pointers$16(VaListTest.java:244) <--------
at VaListTest.testVaListMemorySegment(VaListTest.java:267) <----------
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
This is likely due to the new changes in JDK20 in which MemoryAddress was replaced with MemorySegment. In such case, list.nextVarg on zLinux somehow returns a zero-sized MemorySegment which can't be directly accessed.
I will create a PR in aqa-test to exclude this test suite given everything related to VaList was totally removed in the latest JEP442 (Third Preview) mentioned at #16951 which means there is no need to resolve VaList related issue from now on.
ChengJin01
pushed a commit
to ChengJin01/aqa-tests
that referenced
this issue
Apr 3, 2023
IndexOutOfBoundsException
was captured inVaListTest.testVaListMemorySegment()
on zLinux as follows:against the test code at
https://github.com/ibmruntimes/openj9-openjdk-jdk20/blob/9fcbd19b761da90ae3d1fc9b8692c63e8267d5b7/test/jdk/java/foreign/valist/VaListTest.java#L244
FYI: @tajila, @pshipton
The text was updated successfully, but these errors were encountered: