Hello all.

I have a project whose rake aborts in the current svn revision, a-la :

[EMAIL PROTECTED]:~/.cruise/projects/Myprojectwork$ rake
(in /home/cruisecontrol/.cruise/projects/Myproject/work)
/usr/local/bin/ruby -Ilib:test
"/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb"

/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require':
/home/cruisecontrol/.cruise/projects/Myprojectwork/app/models/customer_quote.rb:3:
syntax error, unexpected kEND, expecting $end (SyntaxError)
    from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require'
    [... yadda yadda ...]
rake aborted!
Command /usr/local/bin/ruby -I [... yadda yadda ... ] failed

The rake "should" be aborting for me, as the customer_quote.rb is : xxclass
CustomerQuote; end which has obvious syntax errors.

yet, builder reports success, from console log of ./cruise start --trace
[debug] /home/cruisecontrol/.cruise/projects/Myproject/work cruisecontrol$
svn --non-interactive update --revision 46
[info]  [2008-08-22 14:44:22] Build 46.1 started
Build 46.1 started
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:71:
warning: conflicting chdir during another chdir block
192.168.0.49 - - [22/Aug/2008:14:44:22 CDT] "GET /projects.js HTTP/1.1" 200
2428
http://test:3333/ -> /projects.js
[debug] [2008-08-22 14:44:24] Sending e-mail to 1 person
[... yadda email ...]
[debug] [2008-08-22 14:44:24] Sent e-mail to 1 person
[info]  [2008-08-22 14:44:24] Build 46.1 finished SUCCESSFULLY
Build 46.1 finished SUCCESSFULLY

Does anyone have a patch for this .... or can direct me to which method call
I can hack to make an aborted rake == build fail ?

Thanks !


Peter Fitzgibbons
(847) 687-7646
Email: [EMAIL PROTECTED]
IM GTalk: peter.fitzgibbons
IM Yahoo: pjfitzgibbons
IM MSN: [EMAIL PROTECTED]
IM AOL: [EMAIL PROTECTED]
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Reply via email to