OpenSearch/test/framework
Simon Willnauer b7bc790428 Use a non default port range in MockTransportService
We already use a per JVM port range in MockTransportService. Yet,
it's possible that if we are executing in the JVM with ordinal 0 that
other clusters reuse ports from the mock transport service and some tests
try to simulate disconnects etc. By using a non-defautl port range (starting at 10300)
we prevent internal test clusters from reusing any of the mock impls ports

Relates to #25301
2017-07-12 22:29:21 +02:00
..
src Use a non default port range in MockTransportService 2017-07-12 22:29:21 +02:00
build.gradle Test that gradle and Java version types match (#24943) 2017-06-02 21:30:47 -04:00