Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test: Use a dedicated port range per test JVM #7396

Merged
merged 1 commit into from Aug 28, 2014

Conversation

Projects
None yet
3 participants
@s1monw
Copy link
Contributor

commented Aug 22, 2014

For reliability and debug purposes each test JVM should use it's own
TCP port range if executed in parallel. This also moves away from the
default port range to prevent conflicts with running ES instance on the local
machine.

@s1monw s1monw added build and removed build labels Aug 22, 2014

@s1monw

This comment has been minimized.

Copy link
Contributor Author

commented Aug 22, 2014

@javanna do you wanna take a look ?

@javanna javanna removed the review label Aug 22, 2014

@javanna

This comment has been minimized.

Copy link
Member

commented Aug 22, 2014

LGTM

[TEST] use a dedicated port range per test JVM
For reliability and debug purposes each test JVM should use it's own
TCP port range if executed in parallel. This also moves away from the
default port range to prevent conflicts with running ES instance on the local
machine.

@s1monw s1monw force-pushed the s1monw:tcp_port_range branch to d062b2b Aug 28, 2014

@s1monw s1monw merged commit d062b2b into elastic:master Aug 28, 2014

@clintongormley clintongormley changed the title [TEST] use a dedicated port range per test JVM Test: Use a dedicated port range per test JVM Sep 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.