Open Haroon-Khel opened 2 years ago
It is possible that these tests fail only in a container environment. The same tests failed on X Linux when run in a docker container https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_linux_testList_1/20/testReport/, but passed when run in a non docker container https://ci.adoptopenjdk.net/job/Grinder/3886/console
For this reason I do not think these failures are non blocking
I agree with you @Haroon-Khel about being non-blocking ... presumably we only have docker environments for this platform at the moment, and can not run these on a different machine to confirm?
While we do not need to block on this, we should look at what we can do in the Docker container to enable ipv6 as that seems to be a common underlying issue for some of these failures:
Unable to resolve host host-ipv6.sample-domain in hosts file TestHosts
and Unable to resolve host ip6-localhost in hosts file /home/jenkins/workspace/Test_openjdk18_hs_extended.openjdk_x86-64_linux_testList_1/aqa-tests/openjdk/openjdk-jdk/test/jdk/java/net/InetAddress/TestHosts-III
re: https://github.com/adoptium/aqa-tests/issues/3487#issuecomment-1078188254 - these tests will become blocking once we want to publish this platform to the Adoptium marketplace, so we should raise an infrastructure issue to get the IPv6 configuration addressed for the static docker hosts.
Test failures from jdk_net_0 during JDK-18+36 Temurin Release Triage on Alpine linux:
It is possible that these tests fail only in a container environment. The same tests failed on X Linux when run in a docker container https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_linux_testList_1/20/testReport/, but passed when run in a non docker container environment https://ci.adoptopenjdk.net/job/Grinder/3886/console