hi, i want to use cc.rb at a client but they, like most rails users, are using the rails recommended ruby 1.8.6. what''s the known issue with this version of ruby with cc.rb and how does it manifest? is there no work around? i can''t really recommend they back-rev their ruby version on their ci server when they''re using 1.8.6 in production and that''s the version that most os x ruby packages come with by default. any suggestions other than an older version of ruby? thanks, -tim -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20071109/c741b0fe/attachment-0001.html
On Nov 9, 2007 3:10 PM, Tim Harding <tim.harding at gmail.com> wrote:> what''s the known issue with this > version of ruby with cc.rb and how does it manifest?I''m so tired by this question... The known question is that test/unit does not exit with non-zero exit code when tests fail in the original 1.8.6 release. This issue has been fixed in 1.8.6 patchlevel 36. -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com]
Hi Alexey, thanks for the prompt answer. Perhaps you could update this: http://cruisecontrolrb.thoughtworks.com/documentation/faq Or put some more details up in the prerequisites section here: http://cruisecontrolrb.thoughtworks.com/documentation/getting_started If you did either of those then I wouldn''t have asked the question. Just to confirm: tim at manhattan:~$ ruby --version ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-darwin8.10.1] Will that be fine along with any patchlevel above 36? Many thanks, -Tim On Nov 9, 2007 10:19 PM, Alexey Verkhovsky <alexey.verkhovsky at gmail.com> wrote:> On Nov 9, 2007 3:10 PM, Tim Harding <tim.harding at gmail.com> wrote: > > what''s the known issue with this > > version of ruby with cc.rb and how does it manifest? > > I''m so tired by this question... > > The known question is that test/unit does not exit with non-zero exit > code when tests fail in the original 1.8.6 release. > This issue has been fixed in 1.8.6 patchlevel 36. > > -- > Alexey Verkhovsky > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > RubyWorks [http://rubyworks.thoughtworks.com] > _______________________________________________ > 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/20071109/59d9fa25/attachment.html
Alexey Verkhovsky wrote:> The known question is that test/unit does not exit with non-zero exit > code when tests fail in the original 1.8.6 release. > This issue has been fixed in 1.8.6 patchlevel 36.which has apparently regressed in patchlevel 110. :( Regards, -- Bil Kleb http://fun3d.larc.nasa.gov
Hi Bil, I got cc.rb all set up with a successful build and then put in a unit test: def test_foo assert false end That caused a build failure so I think that test/unit must be returning a non-zero exit. Are you not seeing the same behaviour? What OS are you on? On Nov 10, 2007 5:15 AM, Bil Kleb <Bil.Kleb at nasa.gov> wrote:> Alexey Verkhovsky wrote: > > The known question is that test/unit does not exit with non-zero exit > > code when tests fail in the original 1.8.6 release. > > This issue has been fixed in 1.8.6 patchlevel 36. > > which has apparently regressed in patchlevel 110. :( > > Regards, > -- > Bil Kleb > http://fun3d.larc.nasa.gov > > _______________________________________________ > 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/20071110/fef28a78/attachment.html
I should add that I''m asking cc.rb to build a Rails app using the default rake tasks. Not sure if that changes matters. On Nov 10, 2007 3:06 PM, Tim Harding <tim.harding at gmail.com> wrote:> Hi Bil, > > I got cc.rb all set up with a successful build and then put in a unit > test: > > def test_foo > assert false > end > > That caused a build failure so I think that test/unit must be returning a > non-zero exit. > > Are you not seeing the same behaviour? > > What OS are you on? > > > > > On Nov 10, 2007 5:15 AM, Bil Kleb <Bil.Kleb at nasa.gov> wrote: > > > Alexey Verkhovsky wrote: > > > The known question is that test/unit does not exit with non-zero exit > > > code when tests fail in the original 1.8.6 release. > > > This issue has been fixed in 1.8.6 patchlevel 36. > > > > which has apparently regressed in patchlevel 110. :( > > > > Regards, > > -- > > Bil Kleb > > http://fun3d.larc.nasa.gov > > > > _______________________________________________ > > 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/20071110/0c43df68/attachment.html