I get the following exception sometimes when I run rake test and I
have some failures/errors in my test cases. It occurs after units/
functionals/integration complete.
Command failed with status (1): [/usr/bin/ruby18 -Ilib:test "/usr/
lib64/rub…]
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:719:in sh' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:incall’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:in sh' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:insh’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:740:in ruby' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:inruby’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:117:in
define' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:823:inverbose’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:102:in
define' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:incall’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:ineach’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:45
/usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:43:in
collect' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:43 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:incall’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:ineach’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:ineach’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:instandard_exception_handling’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:inrun’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in
standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:inrun’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7
/usr/bin/rake:16:in load' /usr/bin/rake:16 rake aborted! Test failures /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:53 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:incall’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:ineach’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:ininvoke’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:ineach’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:instandard_exception_handling’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in
top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:inrun’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in
standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:inrun’
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7
/usr/bin/rake:16:in `load’
/usr/bin/rake:16
I am running ruby 1.8.6 (2007-06-07 patchlevel 36) [x86_64-linux] and
rails 1.2.3, rake 0.7.3
Any ideas? It is just an annoyance because it turns the return code
of rake test to be non zero.
Thanks,
Curtis