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

fixed issue with multiple specs all trying to use same Akka.Remote port at the same time #3817

Merged

Conversation

Aaronontheweb
Copy link
Member

part of #3786

…to use same Akka.Remote port at the same time
@Aaronontheweb
Copy link
Member Author

I think I addressed this inside #3744 using Collection attributes instead of changing the port numbers to 0. Might be a cleaner way of handling this.

@Aaronontheweb
Copy link
Member Author

This is a more heavy-duty change, but I think it's the right way to handle this: if we're going to run the TestSuite concurrently, have everything use port 0 by default. Any HOCON supplied on an individual test will override this.

@Aaronontheweb Aaronontheweb merged commit dbc25db into akkadotnet:dev Jun 26, 2019
@Aaronontheweb Aaronontheweb deleted the 3786_racy_RemotePortBindSpecs branch June 26, 2019 21:03
madmonkey pushed a commit to madmonkey/akka.net that referenced this pull request Jul 12, 2019
…rt at the same time (akkadotnet#3817)

* part of akkadotnet#3786 - fixed issue with multiple specs all trying to use same Akka.Remote port at the same time

* updated specs to use Collections XUnit attribute instead

* use port 0 in all specs by default
Aaronontheweb added a commit to Aaronontheweb/akka.net that referenced this pull request Jul 30, 2019
…rt at the same time (akkadotnet#3817)

* part of akkadotnet#3786 - fixed issue with multiple specs all trying to use same Akka.Remote port at the same time

* updated specs to use Collections XUnit attribute instead

* use port 0 in all specs by default
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.

1 participant