run reel specs in their own process. (possibly solve #126) #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
no such luck, passed once but then failed: https://travis-ci.org/seancribbs/webmachine-ruby/jobs/18501999 |
ghost
closed this
ghost
deleted the
|
I guess port = TCPServer.new('::', 0).addr[1]Would be enough |
|
@Asmod4n i'm not sure. i don't understand the reel problem well enough to come up with a reliable solution. |
ghost
mentioned this pull request
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I haven't done much reliable testing on this yet so I fired off a few builds on CI.
my hope is that by running reel in a separate process we may be able to avoid the bind errors that come up randomly during spec runs with mongrel/hatetepe also involved.
possibly solve #126