On Fri, 28 Jan 2022 15:11:04 GMT, Michael McMahon <micha...@openjdk.org> wrote:
>>> Or is it possible to change the implementation on AIX so the test passes >>> without change? >> >> * Digging into the java guts to map "0.0.0.0" to "127.0.0.1" seems too far >> to me - as I believe interfaces are not suppossed to be "translating" as >> well. >> * If the behavior "0.0.0.0" becomes "127.0.0.1" is an official standard - a >> bug needs to be filed with IBM (which I cannot do) - but we need to also be >> aware that any fix to AIX is not likely to ever be applied on AIX 7.1 TL4 >> (maybe TL5) which are systems used to build distributions. >> * Again - being a noob (or fresh face; fresh meat) the test title is merely >> "PingThis" - where is "This" defined as "0.0.0.0" (if it had been named >> _PingHERE_ I could understand as the alias, iirc, for 0.0.0.0 is "Here". > > Might be better to skip the test then by adding to the header: > > * > * @requires os.family != "aix" > * > rather than the check in the test source >From the description and evaluation of >[JDK-7163874](https://bugs.openjdk.java.net/browse/JDK-7163874) it seems that >skipping this test on AIX would be reasonable. Some operating systems seem to accept 0.0.0.0 as input - and reply with 127.0.0.1. The changes made for JDK-7163874 simply makes sure that such a reply is not rejected as invalid on the ground that the received address is not the same as the input address. If 0.0.0.0 is not a valid input for the underlying operating system, then the test has no object and should probably be skipped. ------------- PR: https://git.openjdk.java.net/jdk/pull/7013
