On 29/05/2019 08:23, Alan Bateman wrote:
AFAIK the SkippedException is a good match for that.
I don't like the dependency on jtreg.SkippedException but if you find it
useful then okay.
Would you prefer to throw AssertionError instead? It's also
a possibility. Chris thought it might be "too strong".
I assume we can remove the other messages added at the
end as they are less useful than printing the value of each network
interface before testing it.
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.
best regards,
-- daniel
