-
-
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
Use JavaTestUtil for all tck #4512
Conversation
b893491
to
49576df
Compare
Test with JDK8 OpenJ9:
JDK11 OpenJ9:
JDK17 OpenJ9:
JDK19 OpenJ9:
JDK20 OpenJ9:
|
f98b2a5
to
4d165c6
Compare
70aadf2
to
dcf0e35
Compare
dcf0e35
to
74e80fb
Compare
de6ccfe
to
9f1f507
Compare
699cd82
to
4696043
Compare
139f2b2
to
77d1f02
Compare
Signed-off-by: Mesbah Alam <Mesbah_Alam@ca.ibm.com>
77d1f02
to
71248e5
Compare
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 @Mesbah-Alam
Was it tested at @smlambert 's end before merging? |
Yes, I ran tests at the temurin-compliance server, thanks for checking @Mesbah-Alam - I should have added a note! |
Perfect, Thanks @smlambert ! |
This reverts commit d4e8916.
This PR replaces JavaTestRunner with JavaTestUtil as the tck automation wrapper.
Impact:
Faster Execution: Absence of JavaTestRunner wrapper means we are using on less JVM instance. The JVM running the actual tests via tck harness jar is not run as a sub-process spawned by the JVM running JavaTeatRunner, but executed directly from playlist. This reduces overall time taken to run JCK builds.
Easy maintenance: Having the ability to specify tck harness parameters directly in the playlist makes each tck playlist command line clearer, easier to maintain and update.
Enhanced debug-ability: Absence of JavaTestRunner wrapper means less redirection hence more debug-ability for failures.
Less overhead in running additional services: Since additional services like rmi registry, rmid, etc, will be launched directly, as opposed to via ProcessBuilder in JavaTestRunner, it should also contribute to overall improved performance of tck builds in Jenkins.
Related to backlog/issues/1013