You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to run spork cuc and spork rspec simultaneously in Windows, I noticed that cucumber will sometimes take tuples created by spork rspec and rspec will sometimes take tuples created by spork cuc. In fact, sometimes both spork processes will take tuples when trying to run a test.
The issue seems to be that although spork listens for DRb requests on different ports for rspec and cucumber, it ends up forwarding the request to the same RingServer instance, which takes the first tuple available regardless of which spork process created it. This seems to be related to #87, but a fix to that might not necessarily resolve this issue.
Rspec trying to run a cucumber feature:
C:/Ruby193/lib/ruby/1.9.1/drb/drb.rb:1095:in `method_missing': Gherkin:: (DRb::DRbUnknownError)
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rspec-core-2.10.0/lib/rspec/core/drb_command_line.rb:19:in `run'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rspec-core-2.10.0/lib/rspec/core/runner.rb:63:in `run'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rspec-core-2.10.0/lib/rspec/core/runner.rb:10:in `block in autorun'
When attempting to run
spork cuc
andspork rspec
simultaneously in Windows, I noticed that cucumber will sometimes take tuples created byspork rspec
and rspec will sometimes take tuples created byspork cuc
. In fact, sometimes both spork processes will take tuples when trying to run a test.The issue seems to be that although spork listens for DRb requests on different ports for rspec and cucumber, it ends up forwarding the request to the same RingServer instance, which takes the first tuple available regardless of which spork process created it. This seems to be related to #87, but a fix to that might not necessarily resolve this issue.
Rspec trying to run a cucumber feature:
Cucumber trying to run a spec:
The text was updated successfully, but these errors were encountered: