-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Capistrano Cucumber features are failing #1743
Comments
Can you post your output please, and try and fulfil some of the fields listed in the issue template that you deleted. |
Sure @leehambley . $ bundle exec rake features Here is my output
[vagrant] . Bundler cannot continue. [vagrant] [vagrant] # from /home/sait/pramati/opensource/capistrano/Gemfile:4 [vagrant] # ------------------------------------------- [vagrant] # # Specify your gem's dependencies in capistrano.gemspec [vagrant] > gemspec [vagrant] # [vagrant] # ------------------------------------------- [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:383:in eval_gemspec' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:344:in block in load_gemspec_uncached'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/shared_helpers.rb:53:in chdir' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/shared_helpers.rb:53:in block in chdir'[vagrant] from /usr/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/shared_helpers.rb:52:in chdir'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:339:in load_gemspec_uncached' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:329:in load_gemspec'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/dsl.rb:56:in gemspec' [vagrant] from /home/sait/pramati/opensource/capistrano/Gemfile:4:in eval_gemfile'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/dsl.rb:36:in instance_eval' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/dsl.rb:36:in eval_gemfile'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/dsl.rb:10:in evaluate' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/definition.rb:24:in build'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:120:in definition' [vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler.rb:88:in setup'[vagrant] from /home/sait/.rvm/gems/ruby-2.2.2/gems/bundler-1.11.2/lib/bundler/setup.rb:18:in <top (required)>' [vagrant] from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require'[vagrant] from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require' pid 32511 exit 1 (VagrantHelpers::VagrantSSHCommandError) ./features/support/vagrant_helpers.rb:31:in run_vagrant_command'./features/step_definitions/assertions.rb:111:in /^an error is raised$/' features/deploy_failure.feature:16:in But an error is raised'Then the failure task will run # features/step_definitions/assertions.rb:98 ` |
Hi, it looks like you are using Bundler 1.11.2. As noted in the DEVELOPMENT documentation, you need to use Bundler 1.10.5 to run the Cucumber features. One way to do that is:
Also, for future reference, when posting output in a GitHub comment use triple backticks (aka "code fences") to ensure proper formatting, as described here: https://help.github.com/articles/creating-and-highlighting-code-blocks/ Thanks for helping out with Capistrano! |
I just tested the feature specs and they pass for me using the above bundler version lock. |
Hi,
When I try to run the capistrano cucumber features they are getting failed.
I installed bundler(1.10.5),Virtual Box and Vagrant. I can see a failure count of 13 features.
I tried running
bundle _1.10.5_ exec rake features
The text was updated successfully, but these errors were encountered: