On 29/05/2019 08:28, Daniel Fuchs wrote:
Would you prefer to throw AssertionError instead? It's also
a possibility. Chris thought it might be "too strong".
It might be odd to have a test system configured without multicast
enabled but it's not wrong. So I think the test should pass.
:
Right - printing interfaces before testing them would be useful.
But printing all interfaces if no multicast was found is useful
too - it might help figure out why the test was not run.
I think it would be useful for tests such as this one to print the
network interface configuration at the start. That might be something
for a supporting method in jdk.test.lib.NetworkConfiguration (if there
isn't anything already).
-Alan
