-
Notifications
You must be signed in to change notification settings - Fork 33
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
Generate different ports for each integration test net. #356
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this feature!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
25ed064
to
df1ccca
Compare
After changing ports, a little issue was identified in network restart test. Test was updated to use a new client connection (using new port) |
- client needed to be regenerated - contract binding object needs to be re-bound using new client.
df1ccca
to
1278d43
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
This change isolates each instance of an integration test by choosing a different (best-effort unused) set of ports, and turning off discovery protocol.
Although tests are currently not segregated, this PR enables the segregation of those into different processes, this change is currently waiting for the memory usage reduction.
This test enables developers to locally run multiple integration tests simultaneously.