[Cruisecontrolrb-users] Problems getting CC.rb running as daemon

[Jeremy Stell-Smith]

fyi, you're going to have some issues w/ 1.8.6 if you're using test unit -
specifically, test::unit never returns an error code of 1 on failing tests,
so cruise will never fail for a unit test.  you can hack around it.
hopefully we'll get a new version of ruby soon

On 9/5/07, Theron Trout <ttrout at stormfish.net> wrote:
>
> Hi Alexey,
>
> I got it.  Ubuntu Feisty is still using Ruby 1.8.5 as the default
> install.  Mongrel 1.0.2 will not work with Ruby 1.8.5.  See
>
> http://www.urbanpuddle.com/articles/2007/08/17/mongrel-cluster-1-0-2-and-ruby-1-8-5
>
>
> I manually installed Ruby 1.8.6 and then reinstalled Rails through ruby
> gems.  Now everything is working just fine.
>
> Thanks again for you help.
>
> Best,
> Theron Trout
>
> Alexey Verkhovsky wrote:
> > On 8/30/07, Theron Trout <ttrout at stormfish.net> wrote:
> >
> >> Are there any known issues with CC.rb on 64 archs?
> >>
> > None, it's pure Ruby.
> >
> >
> >> I get the same result from the daemon and from 'scrip/server -d'.
> >>
> > And what happens if you generate a skeleton Rails app and run that
> > with 'script/server -d'?
> >
> >
> _______________________________________________
> 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/20070907/439607e9/attachment.html