Flaky UT: JettyWithResponseFilterEnabledTest

[paul-rogers]

The UT JettyWithResponseFilterEnabledTest.testExtensionAuthFilter failed in this build:

org.apache.druid.server.initialization.JettyWithResponseFilterEnabledTest
[ERROR] org.apache.druid.server.initialization.JettyWithResponseFilterEnabledTest.testExtensionAuthFilter  Time elapsed: 0.317 s  <<< ERROR!
java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:50684
	at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)

The same test passes locally in an IDE. Conclusion: the test is flaky, likely due to networking issues, or an attempt to run tests in parallel using the same listen port on the host. Jetty allows listening on a random port: tests should use that feature if they don't already do so.

The test attempt to randomize ports:

    final int ephemeralPort = ThreadLocalRandom.current().nextInt(49152, 65535);

However, this is the wrong way to do so. Each run will produce the same sequence of random numbers, unless a random seed is provided. Also, Jetty does this the right way: it chooses a random port and ensures that the port is not in use.

[github-actions]

This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.