-
-
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
Compare AIX openjdk jtreg exclusion list with SAP's #2828
Comments
We observe a large amount of differences between SAP JDK-8 tests excluded in
Versus the one maintained at Adoptium repo
Minimal set of AIX specific test exclusions (tag=aix-all) can be seen at OpenJDK repo: https://github.com/openjdk/jdk8u/blob/master/jdk/test/ProblemList.txt and another few on top of it with tag=generic-all So,
|
One needs also to look at the playlist.xml file also to see if any targets (groups of testcases) are excluded/disabled (over and above single testcases excluded via the ProblemList.txt file). jdk_awt, jdk_security3, jdk_sound, jdk_swing, jdk_client_sanity, jdk_2d, jdk_jfc_demo are currently disabled for all platforms including AIX. jdk_jfr is disabled for AIX. |
Observe various Test groups are listed at jdk, hotspot and langtools For example in jdk Test group file, entry for jdk_security3 looks like
I read the above as : To Summarize, Is this how i should proceed:
Or is there is a better way to accomplish the comparison task? |
Thanks to @ShelleyLambert, Am able to rule out some more tests based on targets disabled in playlist.xml file jdk_swing are currently disabled for all platforms including AIX.
jdk_awt are currently disabled for all platforms including AIX.
jdk_2d are currently disabled for all platforms including AIX.
jdk_security3 are currently disabled for all platforms including AIX
Still a fair way to go for completion |
Following targets are enabled in playlist.xml file, whereas SAP has excluded the specific tests
|
Pending SAP excluded tests to check:
|
Am unsure about how to confirm the pending test case exclusions. If I have access to Jenkins console output when the full suite of test cases was run for AIX platform, perhaps that is one way. If this is the right approach can someone please point me to the Jenkins link. Any help most appreciated. |
Anyone should be able to see the console output of the test runs. Many of the test targets being discussed in this issue are categorized into the extended.openjdk group, which can be found here for jdk8: So looking at a recent job 25, we run it in parallel across 3 machines, you can see the 3 child test jobs and click on each to see their console output, and look at TAP Extended Test Results to see which test targets were included in them, while each of the child jobs Test Result link shows the Junit output of the individual test cases (and you can look at each child's console output also). Same type of traversal can be done for the tests categorized in sanity.openjdk, starting with the top level parent test job at: |
Similar test fail: java/net/httpclient/ManyRequests for openjdk18, aix-ppc64 Jenkins URL: https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_ppc64_aix_testList_0/6/#showFailuresLink java/net/ipv6tests/UdpTest.java.UdpTest for openjdk18, s390x_linux |
Closing this issue as "as done as its going to get". |
We should compare SAP's list of AIX test exclusions as posted to the ppc-aix-port-dev list with the exclusions that we have in this repository, and sync them as appropriate to ensure consistent coverage with the team that had been working on the port as it transitions to another custodian.
The text was updated successfully, but these errors were encountered: