Skip to content

Cucumber hangs after installing frogger #4

Closed
lawrencepit opened this Issue Jul 13, 2011 · 3 comments

2 participants

@lawrencepit

I just added gem 'frogger' to my Gemfile, then ran:

$ cucumber features/example.feature

this hangs after the first step, and CPU maxes out to 100%.

@evolve2k
Owner

Hi Lawrence

Which versions of the following gems are you using:

  • cucumber
  • cucumber-rails
  • frogger

Also - when you kill the process, is there a stack trace?

Cheers

Richie

@lawrencepit

In my Gemfile.lock it says this:

cucumber (1.0.1)
  builder (>= 2.1.2)
  diff-lcs (>= 1.1.2)
  gherkin (~> 2.4.5)
  json (>= 1.4.6)
  term-ansicolor (>= 1.0.5)
cucumber-rails (1.0.2)
  capybara (>= 1.0.0)
  cucumber (~> 1.0.0)
  nokogiri (>= 1.4.6)

frogger (0.2.2)
  colored (>= 1.2)
  cucumber (>= 0.10.0)

Tried again by running rake features. The stacktrace, after killing the process:

Examples: 
  | site      | plan   |
  | Project   | Small  |^C

Exiting... Interrupt again to exit immediately.
^Crake aborted!
Command failed with status (1): [/Users/c/.rvm/rubies/ree-1.8.7-2011.03/...]
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/file_utils.rb:53:in create_shell_runner'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in
call'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in sh'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/file_utils_ext.rb:36:in
sh'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/cucumber-1.0.1/lib/cucumber/rake/task.rb:104:in run'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/cucumber-1.0.1/lib/cucumber/rake/task.rb:193:in
define_task'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:205:in call'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:205:in
execute'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:200:in each'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:200:in
execute'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:158:in invoke_with_call_chain'
/Users/c/.rvm/rubies/ree-1.8.7-2011.03/lib/ruby/1.8/monitor.rb:242:in
synchronize'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:151:in invoke_with_call_chain'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:176:in
invoke_prerequisites'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:174:in each'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:174:in
invoke_prerequisites'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:157:in invoke_with_call_chain'
/Users/c/.rvm/rubies/ree-1.8.7-2011.03/lib/ruby/1.8/monitor.rb:242:in
synchronize'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:151:in invoke_with_call_chain'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:176:in
invoke_prerequisites'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:174:in each'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:174:in
invoke_prerequisites'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:157:in invoke_with_call_chain'
/Users/c/.rvm/rubies/ree-1.8.7-2011.03/lib/ruby/1.8/monitor.rb:242:in
synchronize'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:151:in invoke_with_call_chain'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/task.rb:144:in
invoke'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:112:in invoke_task'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:90:in
top_level'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:90:in each'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:90:in
top_level'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:129:in standard_exception_handling'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:84:in
top_level'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:62:in run'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:129:in
standard_exception_handling'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/lib/rake/application.rb:59:in run'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/gems/rake-0.9.2/bin/rake:32
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/bin/rake:19:in
load'
/Users/c/.rvm/gems/ree-1.8.7-2011.03@rails3/bin/rake:19
Tasks: TOP => features => cucumber => cucumber:ok

Interestingly (perhaps): all scenarios before this one were "normal" scenarios without examples that all succeed. Perhaps it hangs with frogger when trying scenarios that use examples?

@evolve2k
Owner

Hi Laurence

After some head scratching, I've finally uncovered the issue.

When running Examples a collection of scenarios is passed to frogger rather than a single scenario.
I've updated the gem to now handle examples.
The the new version(v0.3.0) now supports examples.
After the first scenario example, each additional scenario example runs with it's own green heading in the log output.

Richie

@evolve2k evolve2k closed this Sep 29, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.