Linux/s390x test case failure in UdpTest on Ubuntu18 systems

[sxa]

Please set the title to indicate the test name and machine name where known.

To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:

• test suite/name? jdk_net_0, UdpTest
• Is there an existing issue elsewhere covering this? https://bugs.openjdk.java.net/browse/JDK-8198266 and excluded via Exclude java/net/ipv6tests/UdpTest.java on s390 with jdk17 aqa-tests#2996 although it has also been seen during 11.0.14 triage. Based on TRSS history it appears to only fail on our Ubuntu 18.04 systems and passes on Ubuntu 16.04, so investigation is required to see whether this is specific to the distribution version, or a configuration on themachine
• Which machine(s) does it work on? Seemingly any Ubuntu 16.04 systems
• Which machine(s) does it fail on? Seemingly any Ubuntu 18.04 systems
• Do you have a link to a Grinder re-run of the test with the failure? Expected Failure on 1804 | Expected pass on 1604

Any other details:

[sxa]

s390x networking - verify how universal it is, whether it was only on the Ubuntu 18 machines, and whether we need to raise with Marist.

[sxa]

We no longer have Ubuntu 18.04 machine for s390x in the CI. Testing on other systems with java/net/ipv6tests/UdpTest.java re-runs. These are using a jdk17u nightly:

Machine / Grinder link	result
test-docker-sles12-s390x-1	✅
test-docker-sles15-s390x-1	✅
test-marist-ubuntu2404-s390x-1	✅
test-marist-ubuntu2204-s390x-1	✅
test-marist-rhel8-s390x-2	✅
test-marist-rhel7-s390x-2	❌ (Timeouts)
test-marist-sles15-s390x-2	✅

Based on the above this seems like a potential candidate for unexclusion, although the referenced bug https://bugs.openjdk.org/browse/JDK-8198266 in the exclusions file is not showing as resolved. While this was initially only excluded on s390x, a subsequent update at https://github.com/adoptium/aqa-tests/pull/3679/files switched it to all platforms. @sophia-guo Can you recall where else we might have seen this test fail since this issue was specific to s390x?

[sxa]

a subsequent update at https://github.com/adoptium/aqa-tests/pull/3679/files switched it to all platforms. @sophia-guo Can you recall where else we might have seen this test fail since this issue was specific to s390x?

Ping @sophia-guo - do you know if this is showing up on other platforms?