# Strange rake behavior

**URL:** <https://www.ruby-forum.com/t/strange-rake-behavior/110303>\
**Category:** Rails\
**Created:** [July 25, 2007, 2:21am UTC](https://www.ruby-forum.com/t/strange-rake-behavior/110303 "2007-07-25T02:21:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gcnovus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/779978/32.png) [@gcnovus](https://www.ruby-forum.com/u/gcnovus)\
**Post date:** [July 25, 2007, 2:21am UTC](https://www.ruby-forum.com/t/strange-rake-behavior/110303/1 "2007-07-25T02:21:03Z")

</div>

I’m getting some really really really odd testing behavior.

1. Running rake test:units passes with flying colors. (Well, that’s  
not what I mean by weird, but I suppose it is 😉 )

2. Running rake test:functionals yields something like  
…E…EEEEE…EEEE…rake  
aborted!  
But doesn’t print any stack traces or error message output for the Es  
(even if I call it with -t for tracing).

3. Running ruby test/functional/\_\_\_\_\_.rb for each of my functional  
tests passes with flying colors.

So my questions are  
a) why no error messages? why no stack traces?  
b) why does rake fail, but direct testing work?

I’m using test-spec and test-spec-on-rails, but everything was working  
a few commits ago.

-Gaius

---

<div class="post-metadata">

**Author:** ![gcnovus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/779978/32.png) [@gcnovus](https://www.ruby-forum.com/u/gcnovus)\
**Post date:** [July 25, 2007, 2:23am UTC](https://www.ruby-forum.com/t/strange-rake-behavior/110303/2 "2007-07-25T02:23:13Z")

</div>

I suppose I should add the stack trace that I get with -t tracing:

Command failed with status (): [/usr/local/bin/ruby -Ilib:test "/usr/  
local…]  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:719:in `sh' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:in`call’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:in `sh' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:in`sh’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:740:in `ruby' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:in`ruby’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:  
117:in `define' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:823:in`verbose’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:  
102:in `define' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`call’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in  
`execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`each’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in  
`execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in`invoke’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in  
`synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in`invoke’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in`each’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in`standard\_exception\_handling’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in  
`top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in`run’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in  
`standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in`run’  
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7  
/usr/local/bin/rake:18:in `load’  
/usr/local/bin/rake:18

That’s for the rake task itself, not for any individual test. None of  
those output anything.

-Gaius