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

UBI and Ubuntu 2404 test failure summary #3614

Open
Haroon-Khel opened this issue Jun 24, 2024 · 10 comments
Open

UBI and Ubuntu 2404 test failure summary #3614

Haroon-Khel opened this issue Jun 24, 2024 · 10 comments
Labels

Comments

@Haroon-Khel
Copy link
Contributor

Haroon-Khel commented Jun 24, 2024

Using this issue to summarise the consistent failures of #3586 and #3501 as there were many common failures

UBI 8 and 9 JDK8 all platforms:
Known issue #2949
java/net/Inet6Address/B6206527.java
java/net/ipv6tests/B6521014.java

both are excluded on linux for openj9 https://github.com/adoptium/aqa-tests/blob/7e3811b9d4c6fcf265d2fc7e9852412034fe6260/openjdk/excludes/ProblemList_openjdk8-openj9.txt#L150 and https://github.com/adoptium/aqa-tests/blob/7e3811b9d4c6fcf265d2fc7e9852412034fe6260/openjdk/excludes/ProblemList_openjdk8-openj9.txt#L166

I recommend exclusion for jdk8

UBI8 and 9
Known issue #2631
java/nio/file/Files/probeContentType/Basic.java

excluded on windows for many jdk versions https://github.com/search?q=repo%3Aadoptium%2Faqa-tests+java%2Fnio%2Ffile%2FFiles%2FprobeContentType%2FBasic&type=code

UBI 8 and 9 and Ubuntu 2404, various tests within jdk_security3 are failing for jdk8 and 11, common ones are

sun/security/pkcs11/fips/TestTLS12.java
sun/security/pkcs11/Provider/Login.sh
sun/security/pkcs11/Secmod/AddPrivateKey.java
sun/security/pkcs11/Secmod/GetPrivateKey.java
sun/security/pkcs11/Secmod/JksSetPrivateKey.java
sun/security/pkcs11/Secmod/LoadKeystore.java
sun/security/pkcs11/Secmod/TrustAnchors.java
sun/security/tools/keytool/autotest.sh

Ubuntu 2404 and UBI 8 and 9, JDK 11 all platforms

java/time/test/java/time/format/TestUTCParse.java

@sxa
Copy link
Member

sxa commented Jun 24, 2024

Notes:

  • Looking at the IPv6 test failures in the issue at infra#2949 it looks like it's passing on some machines and not others on the same host, and with the same OS. Is that correct? In which case we perhaps need to understand the difference instead of just exclude and see if we can make the failing machines work (Assuming this new problem is that same as that one in that issue). Also noting that the -1 machine mentioned in that issue as having been taken offline is now live again.
  • Most of the pkcs11/JDK8 ones are covered by JDK8: Failing pkcs11 tests (libnss related?) on AL2023, UBI9+, F35+ aqa-tests#5380
  • The exception to the issue in the previous bullet point is TestTLS12 which was noted in the April triage as passing when run on our RHEL6 host, so this likely needs a new issue raised to look at it. infra#2625 suggests there is a fix for this, although it has now been excluded specifically on Linux/ppc64le
  • autotest.sh failure was seen on Amazon Linux 2023 although this comment suggests it passed on an Ubuntu 24.04 system.
  • Also noting that it's interesting that the IBM943 failure in the nio suite has not been seen on UBI, so that appears to have been Amazon linux specific
  • TestUTCParse has been noted elsewhere (including macos) e.g. April triage but I don't believe an issue has been raised, so that should be done.
  • Is the java nio Basic test specific to JDK8 too? And if so does that mean JDK17+ are all ok on Ubuntu 24.04 (Which seems consistent with the riscv64 testing at Replace Ubuntu 23.10 Scaleway machines with 24.04 LTS #3598

@Haroon-Khel
Copy link
Contributor Author

Raised #3658 for the failing TestUTCParse test

@Haroon-Khel
Copy link
Contributor Author

There also 2 more tests affecting JDK21 for both UBI8/9 and Ubuntu2404

jdk/jfr/jcmd/TestJcmdDump.java
com/sun/jdi/FinalizerTest.java

@smlambert
Copy link
Contributor

There also 2 more tests affecting JDK21 for both UBI8/9 and Ubuntu2404

Noting from our discussion that TestJcmdDump and FinalizerTest are intermittent failures that are considered non-blocking. (OutOfMemory)

@sxa
Copy link
Member

sxa commented Jul 5, 2024

We had a call today to discuss some of these failures with a goal to get approval to support Ubuntu 24.04 for the July release:

@Haroon-Khel
Copy link
Contributor Author

Haroon-Khel commented Jul 5, 2024

@Haroon-Khel will try to install the shared-mime-info package referenced in #2631 (comment) to see if ti resolves the probeContentType failure (Noting that the equivalent package on Ubuntu may be different)

Installing shared-mime-info allows the test to pass. Ive installed it on all of the affected machines and will add it to the dockerstatic dockerfiles

@Haroon-Khel
Copy link
Contributor Author

@Haroon-Khel will attempt a run of the TestUTCParse test after adjusting the time zone on the machine to UTC

On the failing machines it looks like the time is already set to UTC

root@test-azure-ubuntu2404-x64-1:~# date
Fri Jul  5 16:37:29 UTC 2024

@smlambert
Copy link
Contributor

smlambert commented Jul 5, 2024

On the failing machines it looks like the time is already set to UTC

and looking at passing machines do you see differences in output of date?

@sxa
Copy link
Member

sxa commented Jul 9, 2024

Noting that based on the table at adoptium/aqa-tests#5420 (comment) I'm ok with the PKCS11 and TestTLS12 failures being no worse on Ubuntu 24.04 than on 22.04 so I do not consider that a blocker.
Also @smlambert just to clarify the autotest.sh failure does not occur on Ubuntu 24.04 so is not a blocker for that version.

@Haroon-Khel
Copy link
Contributor Author

and looking at passing machines do you see differences in output of date?

On test-docker-alpine319-x64-4 on which the test passes (https://ci.adoptium.net/job/Grinder/10549/console)

8f585a2be287:/# date
Tue Jul  9 15:57:37 UTC 2024

Same format as #3614 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants