[Cruisecontrolrb-users] reporting failures

itsdave101 at gmail.com itsdave101 at gmail.com
Wed Feb 27 17:33:30 EST 2008


On Tue, Feb 26, 2008 at 11:29 PM, Chad Woolley <thewoolleyman at gmail.com>
wrote:

> On Tue, Feb 26, 2008 at 11:15 PM, itsdave101 at gmail.com
> <itsdave101 at gmail.com> wrote:
> > Finished in 6.445108 seconds
> >
> > 450 examples, 2 failures, 91 pending
> > rake aborted!
> >
> > yet, cruisecontrolrb still reports success.
> >
> >
> > any ideas?
>
> Look closely at the return code of your rake tasks, or however you
> invoke your tests/specs.  Try running them manually, outside of
> cruise, and inspect the return code ($?).  See if you can track down
> the false positive return code.
>
> -- Chad



I think i figured it out. seems I should be using

Rake::Task["spec"].invoke

as opposed to

system "rake spec"

found my answer here:
http://railsbros.de/2007/11/19/rake-code-cruise-code-task

David.




>
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080227/4c6005fe/attachment.html 


More information about the Cruisecontrolrb-users mailing list