On Sun, 23 Feb 2025 12:46:53 GMT, Alan Bateman <al...@openjdk.org> wrote:
>> Hi all,
>>
>> Four sun/management/jdp tests fails "java.net.SocketException: No such
>> device" on some machines. The machine cannot connect to the Internet
>> directly and needs to be connected to the Internet through a jump machine.
>> The sun/management/jdp tests report "java.net.SocketException: No such
>> device" failure do not caused by JVM bug but environmentalk issue, so this
>> PR match the output and throw `jtreg.SkippedException` instead of report
>> test fails.
>>
>> Change has been verified locally, test-fix only and make tests more
>> robustness, no risk.
>
> test/jdk/sun/management/jdp/DynamicLauncher.java line 66:
>
>> 64: if (output.contains("java.net.SocketException: No such device"))
>> {
>> 65: throw new SkippedException("Network setup issue, skip this
>> test");
>> 66: }
>
> Something else isn't right if you are getting this error so I think further
> investigation is required to see if the issue is the test choosing the wrong
> interface or address, or a configuration issue on the test system.
The tested address:port is hard code to '224.0.23.178:7095' by file
test/jdk/sun/management/jdp/ClientConnection.java. This address:port work
normally on most machines, but cannot work on machine which can not connect to
the internet directly.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/23738#discussion_r1966784435
