-
-
Notifications
You must be signed in to change notification settings - Fork 102
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 still fail on Aix machines #2516
Comments
Ping @aixtools |
|
Trying to get the failing tests narrowed down, trying TARGET: jdk_net now (jdk_net_0 didn't seem to do anything). |
This is the failed test URL - FOR RESTARTS! Change the JDK version for the different tests : from Grinder #4245 |
|
I'll need some assistance with setting up a way to test changes in openjdk itself, e.g., a change in java.base/sun.nio.ch.DatagramChannelImpl.innerJoin(DatagramChannelImpl.java (that is not part of the aqu-tests).
|
Sigh: Thought I had saved the parambuild URL - but sadly not. From testing on the java8: when two interfaces are defined - it fails on the interface with no (default) route. When that interface is detached, the 'JoinLeave' test succeeds.
|
@Haroon-Khel : can you initiate this test again. I have forgotten how to regenerate from the data above. |
fyi: this test fails for two reasons: a) the test incorrectly believes AIX is running an active world IPv6 address. By default the IPv6 stack is active - for lo0 and address ::1 My recommendation is to put this test on the 'skip' list - as it will take forever if upstream is fast. Never is the more likely stream for getting this fixed upstream. |
Again, the tests - as written, do not account for the way that AIX reacts to NULL (rather than empty string Since 1999 (when AIX 4.3 came out - if not earlier (AIX 4.2 might have already had it) - Further, at OSUOSL the only other interface to have an IPv6 address, if there is one, is imho: until behavior is studied in detail - skip the tests failing. iirc, the failure comes from a common routine in all the tests that fails before any actual new test component gets tried. Been 18+ months since I studied this. Responses from upstream were just too slow to get anything finished. Too many layers protecting their forums from spam posters. Or something like that. |
Some ipv6 tests continue to fail on all of our aix machines. The tests being:
java/net/DatagramSocket/DatagramSocketExample.java.DatagramSocketExample
java/net/DatagramSocket/DatagramSocketMulticasting.java.DatagramSocketMulticasting
java/net/MulticastSocket/SetOutgoingIf.java.SetOutgoingIf
java/net/MulticastSocket/JoinLeave.java.JoinLeave
java/net/MulticastSocket/Promiscuous.java.Promiscuous
java/nio/channels/DatagramChannel/AdaptorMulticasting.java.AdaptorMulticasting
Fail with
It is known upstream that these tests will fail if ipv6 is not correctly configured https://bugs.openjdk.java.net/browse/JDK-8278122
These tests belong to the jdk_net test target. Most recent failure was during the jdk18+36 release https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_ppc64_aix_testList_0/24/testReport/
The text was updated successfully, but these errors were encountered: