Error when running with Rails4, Ruby2 #42
Comments
|
I should note, it's the same error on 1.9.3 - so it seems like a Rails4 thing. |
|
Hi @johnbeynon I haven't been able to reproduce your issue. I've created a skeletal rails app attempting to, but I think I'm missing some details. I've added you as a collaborator to https://github.com/cpb/guard-cucumber-issue-42 -- could you tweak it to reproduce? Cheers, |
|
it's so weird, I've been trying to duplicate it in the app but I just can't and somehow in doing so I've managed to get rid of the error that was appearing in mine. Grrrr. |
|
Still happening for me. Reopen? |
|
@marnen I've added you to my repo that I encouraged @johnbeynon to try and create a repro with. Please push your repro steps to my repo |
|
I will try to look at this tomorrow. (@johnbeynon: nice to see a fellow former Fuseboxer in the Rails world!) |
|
I too reproduced this issue today with vanilla Rails 4 on Ruby 2.p247, cucumber-rails & guard-cucumber. I've created a script to reproduce it at https://gist.github.com/paulspencerwilliams/6131755 |
|
@paulspencerwilliams I got it to reproduce with your script with slight modifications: https://gist.github.com/cpb/6187945 |
|
@paulspencerwilliams my latest revision of your repo.sh (omits rspec) and passes... https://gist.github.com/cpb/6187945/revisions |
|
@cpb strange. I've tried mine, and your two amended scripts and agree with your summary. I also notice that running my script, and your first amendment presents the error on Guard startup. It then repeatedly outputs the error if you invoke 'cucumber' within Guard, but not 'rspec'. Therefore it certainly seems linked to cucumber :-/ Can you advise anything else I can do to help track it down? I'm more than happy to help if I can! |
|
I am encountering this bug presently on a project I am working on. https://gist.github.com/cpb/6187945 -- changes the sequence, with cucumber first I just need to get a bigger stack trace now... |
|
Well if not a bigger stack trace: ["--color",
"--format",
"progress",
"--strict",
"--require",
"/Users/caleb/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-cucumber-1.4.0/lib/guard/cucumber/notification_formatter.rb",
"--format",
"Guard::Cucumber::NotificationFormatter",
"--out",
"/dev/null",
"--require",
"features",
"features"]Checkout what cucumber is doing to |
|
A much more interesting stack trace (though, more of a [
#...
"gems/activesupport-4.0.0/lib/active_support/testing/autorun.rb:5:in `<top (required)>'",
"gems/railties-4.0.0/lib/rails/test_help.rb:5:in `<top (required)>'",
"gems/cucumber-rails-1.3.0/lib/cucumber/rails.rb:11:in `<top (required)>'",
"BugReproduce/features/support/env.rb:7:in `require'",
"BugReproduce/features/support/env.rb:7:in `<top (required)>'",
#...
] |
|
@johnbeynon this is a bug from cucumber/rails that apparently has been solved in master 17 hours ago |
|
and then it was reverted |
|
I''m getting the same error. I'm using Ruby 2 and Rails 4, the cucumber-rails gem at version 1.4.0, so as is the guard-cucumber gem. |
|
My stack trace was the following: |
|
Bundling cucumber-rails at edge seems to solve this for me. |
When running guard-cucumber I get the following output at the end of tests;
i don't get this if I run
cucumberdirectly from the command line.I'm not sure where to start looking.
The text was updated successfully, but these errors were encountered: