2d090d4547
Using a fixed port could cause a false negative, if the port is currently in use. We actually see this test failing regularly with an error that port `1111` is already in use. Quick search did not show any tests that hardcode port 1111, so it is unclear why is this happening. But using hardcoded ports is not a good practice anyways. |
||
|---|---|---|
| .. | ||
| benches | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.toml | ||
| build.rs | ||