Skip to content

Assign unbound port numbers in test instances#255

Merged
byeongjee merged 3 commits intoCodeChain-io:masterfrom
byeongjee:use.unbound.port
Mar 16, 2020
Merged

Assign unbound port numbers in test instances#255
byeongjee merged 3 commits intoCodeChain-io:masterfrom
byeongjee:use.unbound.port

Conversation

@byeongjee
Copy link
Contributor

Resolves #254

Port numbers assigned to test Foundry instances should be unbound.
If the port is already in use, the test will fail, which is not an intended behavior.

@byeongjee byeongjee requested a review from majecty March 12, 2020 06:08
@byeongjee byeongjee force-pushed the use.unbound.port branch 2 times, most recently from 453f262 to 63b461f Compare March 12, 2020 06:19
Copy link

@majecty majecty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please run formatter.

@byeongjee byeongjee force-pushed the use.unbound.port branch 2 times, most recently from 5524dee to 5f99c51 Compare March 12, 2020 06:35
majecty
majecty previously approved these changes Mar 12, 2020
Port numbers assigned to test Foundry instances should be unbound.
If the port is already in use, the test will fail, which is not an intended behavior.
@byeongjee byeongjee requested a review from majecty March 16, 2020 01:09
@byeongjee byeongjee merged commit 3255621 into CodeChain-io:master Mar 16, 2020
@byeongjee byeongjee deleted the use.unbound.port branch March 16, 2020 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Assign unbound port numbers in e2e tests

2 participants