fix: Cargo test failure in Windows environment #108
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you run
cargo test
in a Windows environment, a failure occurs. (This is written in Issue #107.) Here is the issue:The reason why this happens is that Windows uses different system commands than Unix-based operating systems.
Therefore, the command to check the port occupancy status and the command to release the port occupancy are different between Windows and Unix.
losf
, then in a Windows environment it isnetstat
.kill
, then in Windows it istaskkill
.For that reason, I modified the code in that part so that I can check the OS environment and issue instructions with commands appropriate for the OS. With this code change,
test test_static_bootstrap
now succeeds, buttest test_dynamic_bootstrap
still fails.The error that occurs in this regard is:
It looks like this error is occurring because the gRPC connection is refused.