Fix issue 220/sandboxserver port conflict #221
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.
#220
Resolve sanbox server port conflict by adding file lock to sync all
SandboxWorker.init()
methods, so one available port won't be used twice between testcases.Before add global file lock, two sanboxServer may detecte one port as available in calling
SandboxWorker.defaultConfig()
before they runing their local nodes with the port as a params in callingSandboxServer.start()
in:Now, I add the file lock to
So, I added a file lock to preotect instruction from
const defaultConfig = await this.defaultConfig()
toawait worker.server.start()
to avoidavailable
ports conflict between testfiles