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

[Test/FFI] Remove the struct padding on Windows & zLinux #16628

Conversation

ChengJin01
Copy link
Contributor

The changes follow the same rules on the struct-based test cases on Windows & zLinux,
in which case the struct padding is not required in upcall. In addition to that, part of test
cases in JDK17 are updated to remove the unused test code in upcall.

Fixes: #16619

Signed-off-by: ChengJin01 jincheng@ca.ibm.com

@ChengJin01
Copy link
Contributor Author

Verified in Grinders (x10) on all supported platforms including Windows & zLinux for JDK17 & 19
https://openj9-jenkins.osuosl.org/job/Grinder/1924/console (JDK17)
https://openj9-jenkins.osuosl.org/job/Grinder/1933/console (JDK19)

The changes follow the same rules on the struct-based
test cases on Windows & zLinux, in which case the struct
padding is not required in upcall. In addition to that,
part of test cases in JDK17 are updated to remove the
unused test code in upcall.

Fixes: eclipse-openj9#16619

Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
@ChengJin01 ChengJin01 force-pushed the ffi_test_remove_struct_padding_win_zlinux branch from 75514cc to 19d8dd3 Compare January 30, 2023 20:38
@ChengJin01
Copy link
Contributor Author

Reviewer: @tajila
FYI: @pshipton

@tajila
Copy link
Contributor

tajila commented Jan 30, 2023

jenkins test sanity zlinux,win jdk19

@ChengJin01
Copy link
Contributor Author

I didn't see any test failure at https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_sanity.functional_x86-64_windows_Personal/90/tapResults/ or https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk19_j9_sanity.functional_x86-64_windows_Personal/90/

ok 126 - Jep424Tests_testLinkerFfi_UpCall_0 <----- this is our upcall test being verified in JDK19
  ---
    duration_ms: 8390
  ...

Not sure why Test_openjdk19_j9_sanity.functional_x86-64_windows_Personal/90/ was set to FAILURE.

@tajila
Copy link
Contributor

tajila commented Jan 31, 2023

There was an infra failure

Cannot run copyArtifacts from test.getDependency. Skipping copyArtifacts...
[Pipeline] fileExists
18:39:38  win2019-x64-4a was marked offline: Connection was broken: java.io.EOFException
18:39:38  	at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:3001)
18:39:38  	at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3496)
18:39:38  	at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:1058)
18:39:38  	at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:415)
18:39:38  	at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49)
18:39:38  	at hudson.remoting.Command.readFrom(Command.java:142)
18:39:38  	at hudson.remoting.Command.readFrom(Command.java:128)
18:39:38  	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
18:39:38  	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61)
18:39:38  Caused: java.io.IOException: Unexpected termination of the channel
18:39:38  	at hudson.remoting.SynchronousCommandTranspo

@tajila tajila merged commit e57d584 into eclipse-openj9:master Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants