Cucumber test fails: System stack too deep #622

Closed
fespinoza opened this Issue Aug 14, 2012 · 10 comments

Projects

None yet

6 participants

@fespinoza

Hi,

I just cloned the repo and install pigments and all dependencies with bundler

I have installed jekyll too, and it's working with my personal site.

I can run the bundle exec rake test successfully but the bundle exec rake features fails with the following trace

~/code/open source/jekyll git:(master) ➜  bundle exec rake features --trace
** Invoke features (first_time)
** Execute features
/Users/fespinoza/.rbenv/versions/1.9.3-p194/bin/ruby -S bundle exec cucumber --format progress
Using the default profile...
..F-...F-....F-.....F-.............F--------....F-.....F-.....F-.....F-..F-.....F-.....F-.....F-.....F-.....F-.....F---.....F------------.F--.F--.F------------F--F--F--....F-....F-.....F---....F-....F-....F-.....F-.....F-.....F-.....F-.....F-......F-.....F-.......F-.....F-.....F-....F--.....F-.....F--....F-...F-.....F--.....F--...F-...F-...F-...F-...F-........F---........F---....F---....F--........F---..F-..F-....F-....F-....F-....F-....F-...F-

(::) failed steps (::)

/Users/fespinoza/.rbenv/versions/1.9.3-p194/bin/cucumber:23: stack level too deep (SystemStackError)
rake aborted!
Command failed with status (1): [/Users/fespinoza/.rbenv/versions/1.9.3-p19...]
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/file_utils.rb:53:in `block in create_shell_runner'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/file_utils.rb:45:in `call'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/file_utils.rb:45:in `sh'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/file_utils_ext.rb:39:in `sh'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/cucumber-1.1.0/lib/cucumber/rake/task.rb:104:in `run'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/cucumber-1.1.0/lib/cucumber/rake/task.rb:193:in `block in define_task'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:205:in `call'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:205:in `block in execute'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:200:in `each'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:200:in `execute'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:158:in `block in invoke_with_call_chain'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:151:in `invoke_with_call_chain'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/task.rb:144:in `invoke'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:116:in `invoke_task'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:94:in `block (2 levels) in top_level'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:94:in `each'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:94:in `block in top_level'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:88:in `top_level'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:66:in `block in run'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/lib/ruby/1.9.1/rake/application.rb:63:in `run'
/Users/fespinoza/.rbenv/versions/1.9.3-p194/bin/rake:32:in `<main>'
Tasks: TOP => features

and these are my gems for the project

Using rake (0.9.2.2) 
Using RedCloth (4.2.9) 
Using blankslate (2.1.2.4) 
Using builder (3.0.0) 
Using fast-stemmer (1.0.1) 
Using classifier (1.3.3) 
Using diff-lcs (1.1.3) 
Using json (1.7.4) 
Using gherkin (2.5.4) 
Using term-ansicolor (1.0.7) 
Using cucumber (1.1.0) 
Using directory_watcher (1.4.1) 
Using ffi (1.0.11) 
Using kramdown (0.13.7) 
Using liquid (2.4.0) 
Using syntax (1.0.0) 
Using maruku (0.6.0) 
Using rubypython (0.5.3) 
Using pygments.rb (0.2.13) 
Using jekyll (0.11.2) from source at . 
Using rdiscount (1.6.8) 
Using rdoc (3.12) 
Using redcarpet (1.17.2) 
Using redgreen (1.2.2) 
Using rr (1.0.4) 
Using shoulda (2.11.3) 
Using bundler (1.1.4) 
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.

I'm using

  • mac osx mountain lion
  • rbenv
  • ruby 1.9.3-p194

I hope can help me finding the cause of maybe it's a bug in some gem or the project itself

@scribu
Contributor
scribu commented Feb 9, 2013

I am no longer getting this error if I use cucumber 1.2, instead of the specified 1.1.

@parkr
Member
parkr commented Mar 19, 2013

It's still happening on travis every once in a while. It's a weird cucumber issue.

@parkr parkr closed this Mar 19, 2013
@parkr
Member
parkr commented Mar 19, 2013

(And we're using Cucumber 1.2.1 now.)

@jhn
jhn commented Apr 19, 2013

@parkr I'm getting the same thing when using Ruby 1.9.3, Cucumber 1.2.3 and RVM 1.19 on OS X 10.8.3. Any workarounds?

@parkr
Member
parkr commented Apr 19, 2013

I still only get 1 occasionally, like on Travis. Maybe try a different patch version of 1.9.3?

@maul-esel
Contributor

I get it always when

a) any of the features fails or
b) the /tmp/jekyll folder does still exist from a previous failed run

@jhn
jhn commented Apr 19, 2013

@parkr I tried 194, 286, 327 and 392 and Cucumber 1.2.2, 3, 5. Every time I do rake features I get lots of failed tests + the same error the person who opened this issue was getting.

@scribu
Contributor
scribu commented May 23, 2013

I think these lines from features/support/env.rb are the culprit:

World do
  include Test::Unit::Assertions
end

I tried to use the code from that file in a different project and was getting the error. If I removed them, it worked fine.

@parkr
Member
parkr commented May 23, 2013

Oh, interesting! @jhn @maul-esel Does commenting this out and including the unit test assertions elsewhere fix this for you?

@scribu
Contributor
scribu commented May 23, 2013

See #1139

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.