-
-
Notifications
You must be signed in to change notification settings - Fork 102
OpenJDK test B8312065 cannot connect to network on test-docker-ubuntu2404-armv8-6 #4300
Copy link
Copy link
Open
Description
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 (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET): java/net/Socket/B8312065.java
- Recent
Test_link to ci.adoptium.net that shows the failure: https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_aarch64_linux_testList_1/54/- Recent rerun here: https://ci.adoptium.net/job/Grinder/16872/
- Specific error text (if applicable):
16:46:53 Exception in thread "main" java.net.SocketException: Network is unreachable (connect failed)
16:46:53 at java.net.PlainSocketImpl.socketConnect(Native Method)
16:46:53 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
16:46:53 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
16:46:53 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
16:46:53 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
16:46:53 at java.net.Socket.connect(Socket.java:607)
16:46:53 at B8312065.main(B8312065.java:77)
- Hyperlink to re-run in Grinder: Grinder launcher
- Any existing issues covering this: This issue may have some overlap: RISC-V test plan aqa-tests#4976
- Machine(s) this test works on:
- Machine(s) this test fails on: test-docker-ubuntu2404-armv8-6
Any other details:
It looks like this issue is due to the test not handling the SocketException properly when we try to connect to a broadcast address on Ubuntu.
JDK11 and 17 have been changed to catch the SocketException and throw a SkippedException. The PR can be found here, and the bug itself can be found here.
I've added a comment to propose backporting the fix to JDK8, but since this could be mistaken for a problem with the machine itself, I'm raising this issue to clarify the situation.
Reactions are currently unavailable