Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

space/default_instance and space/server use the same port #174

Closed
Totktonada opened this issue Jun 13, 2018 · 2 comments
Closed

space/default_instance and space/server use the same port #174

Totktonada opened this issue Jun 13, 2018 · 2 comments
Labels
archived testing wontfix This will not be worked on

Comments

@Totktonada
Copy link
Member

These two tests sporadically (rarely) run simultaneously on different workers that leads to 'Address already in use' error.
@Totktonada
Copy link
Member Author

Proposed fix: add use_random_port options to bind on port 0 and return choosen port. Use this option in tests.

Totktonada added a commit that referenced this issue Aug 19, 2018
@Totktonada
Run space suite in sequence to prevent port clash
3ee5801 
Workaround for #174.
Totktonada added a commit that referenced this issue Sep 3, 2018
@Totktonada
testing: run space suite in sequence
2e17d48 
It is to prevent port clash.

Workaround for #174.
@Totktonada Totktonada added wontfix This will not be worked on archived and removed prio3 labels Apr 13, 2022
@Totktonada
Copy link
Member Author

I'm going to archive the repository. I'll proceed as follows:

  • Mark all open pull requests with the archived label and close.
  • Mark all open issues with archived and wontfix labels and close.
  • Archive the repository.

Consider the following projects:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
archived testing wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Totktonada