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

IPv6 tests failing on test-docker-ubuntu2204-ppc64le-1 #2949

Open
Haroon-Khel opened this issue Feb 22, 2023 · 6 comments
Open

IPv6 tests failing on test-docker-ubuntu2204-ppc64le-1 #2949

Haroon-Khel opened this issue Feb 22, 2023 · 6 comments

Comments

@Haroon-Khel
Copy link
Contributor

ref #2883 (comment)

java/net/Inet6Address/B6206527.java and java/net/ipv6tests/B6521014.java fail on https://ci.adoptium.net/computer/test-docker-ubuntu2204-ppc64le-1/

Latest failures

java/net/Inet6Address/B6206527.java
https://ci.adoptium.net/view/Test_grinder/job/Grinder/6711/console

java/net/ipv6tests/B6521014.java
https://ci.adoptium.net/view/Test_grinder/job/Grinder/6716/console

This static docker container runs on dockerhost-skytap-ubuntu2204-ppc64le-1, which also hosts test-docker-ubuntu2204-ppc64le-2. The tests pass on -2 but fail on -1

Latest pass on -2

java/net/Inet6Address/B6206527.java
https://ci.adoptium.net/view/Test_grinder/job/Grinder/6712/console

java/net/ipv6tests/B6521014.java
https://ci.adoptium.net/view/Test_grinder/job/Grinder/6717/console

On any new ubuntu2204 container created on dockerhost-skytap-ubuntu2204-ppc64le-1 the tests will fail.

I've taken -1 offline and recommend keeping it so until this is resolved

@sxa
Copy link
Member

sxa commented Nov 5, 2024

Maybe verify if the parameter that @sophia-guo added recently for the reproducible test comparison makes any difference to this.
Maybe also verify that the correct IPv6 options are on this dockerhost, and confirm that other containers on the host are affected or whether it's specific to Ubuntu 2204 (and later?)

@sophia-guo
Copy link

For reproducible tests this is solved by configuring namespaced kernel parameters (sysctls) at runtime (--sysctl). Note Docker does not support changing sysctls inside of a container that also modify the host system. https://github.com/adoptium/temurin-build/pull/4020/files

@sxa
Copy link
Member

sxa commented Nov 7, 2024

For reproducible tests this is solved by configuring namespaced kernel parameters (sysctls) at runtime (--sysctl). Note Docker does not support changing sysctls inside of a container that also modify the host system. https://github.com/adoptium/temurin-build/pull/4020/files

@sophia-guo Do you have an example of a machine where it failed without those parameters? I'm interested to see of the IPv6 options are incorrect on the host.

@sxa
Copy link
Member

sxa commented Nov 7, 2024

Also related (from the dim and distant past) #1105

@sophia-guo
Copy link

sophia-guo commented Nov 7, 2024

There are 4 agents for tests https://ci.adoptium.net/label/ci.role.test&&hw.arch.x86&&sw.os.linux&&!%28centos6%7C%7Crhel6%29&&sw.tool.docker/

It happened to test-azure-ubuntu2404-x64-1 test-ibmcloud-rhel7-x64-1 test-ibmcloud-ubuntu1604-x64-1. I'm not sure if it happened to test-aws-rhel8-x64-1.

Same issue for ppcle64 https://ci.adoptium.net/view/Test_system/job/Test_openjdk21_hs_special.system_ppc64le_linux/2/
aarch64 hhttps://ci.adoptium.net/job/Test_openjdk21_hs_special.system_aarch64_linux/2/

@sxa
Copy link
Member

sxa commented Nov 8, 2024

Great info. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

3 participants