Terasology / Terasology/ModuleTestingEnvironment
"Connection refused" errors when attempting parallel test execution
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
During https://github.com/MovingBlocks/Terasology/issues/4576 I noticed that running tests with --parallel sometimes resulted in an error Connection refused: localhost/127.0.0.1:25777, which I haven't seen in other test runs.
I didn't dig in to the details, but I'm guessing multiple processes were probably trying to use the same ports at once. If that's the case, either
a. they shouldn't be trying to use network ports at all, or
b. they need some smarter port-allocation logic that's muchmuch less likely to have collisions with other instances.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with parallel test execution using --parallel and tracing the localhost:25777 connection path. Determine whether concurrent processes share or collide on network ports; done means parallel tests complete without intermittent Connection refused errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100