-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
guard with parallel_tests fails #167
Comments
Could you try with the just released version 2.5.1 ? |
Yes it works now. Thanks! |
@thibaudgg I'm still getting this error ( guard :rspec, zeus: true, run_all: { parallel: true, parallel_cli: '-n 4' } do
# ...
end Versions:
Any ideas? |
And with just zeus & parallel_tests (without guard) you didn't get it? |
@thibaudgg zeus works fine on it's own, parallel_tests works fine on its own, and both work fine with guard actually, as long as they're both enabled for all tests. It's the exact configuration above that fails, and only when I run a single spec without parallel_tests first, then try running all specs with parallel_tests. It's almost as if the configuration is getting cached or munged somehow from the previous run. I do have an |
Really strange edge-case, I don't use zeus or parallel_tests so I don't know how to fix it. |
I'm having the same issue... any ideas where to start debugging? |
I get the following output when configuring guard to use parallel_test.parallel_tests runs normally through rake.
/Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/gems/parallel_tests-0.10.0/lib/parallel_tests/cli.rb:65:in
'parse_options!': invalid option: -f (OptionParser::InvalidOption) from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/gems/parallel_tests-0.10.0/lib/parallel_tests/cli.rb:6:in
run'from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/gems/parallel_tests-0.10.0/bin/parallel_rspec:5:in
<top (required)>' from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/bin/parallel_rspec:19:in
load'from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/bin/parallel_rspec:19:in
<main>' from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/bin/ruby_noexec_wrapper:14:in
eval'from /Users/i0n/.rvm/gems/ruby-1.9.3-p392@global/bin/ruby_noexec_wrapper:14:in `
Looks like it is trying to pass RSpec options to parallel_tests?
The configuration looks like this:
guard 'rspec', :parallel => true, :parallel_cli => '-n 2' do
.... stuff....
end
Gems:
rspec: 2.13.0
parallel_tests: 0.10.0
guard: 1.6.2
guard-rspec: 2.5.0
The text was updated successfully, but these errors were encountered: