Levent Ali
2007-Apr-04 14:06 UTC
[Cruisecontrolrb-users] Reporting as fixed even though there are test failures
Even though there are errors and failures in our tests Cruise Control is reporting the build is NOT broken and thus not emailing anybody... aspire_rails_12x build 1818 finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds Build Changeset Revision 1818 committed by katem on 2007-04-04 12:47:28 removed breakpoint M /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb Test Failures and Errors Name: test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) Type: Failure Message: <1> expected but was <2>. ./test/unit/question_set_element_test.rb:328 Name: test_new_step_must_have_site_id(RegistrationWizardStepTest) Type: Failure Message: <1> expected but was <2>. ./test/unit/registration_wizard_step_test.rb:31 Name: test_run(TalentPoolNotificationsTest) Type: Failure Message: <3> expected but was <0>. ./test/unit/talent_pool_notifications_test.rb:60 Any ideas why this may be? cheers Levent
Jeremy Stell-Smith
2007-Apr-04 15:39 UTC
[Cruisecontrolrb-users] Reporting as fixed even though there are test failures
Are you using Ruby 1.8.6? There is a bug with Ruby 1.8.6 that is causing Test::Unit to return the incorrect exit code, and cruise not to fail. For now, the fix is to go back to Ruby 1.8.4 or 1.8.5. We''re working on a better workaround. On 4/4/07, Levent Ali <levent at leventali.com> wrote:> > Even though there are errors and failures in our tests Cruise Control > is reporting the build is NOT broken and thus not emailing anybody... > > aspire_rails_12x build 1818 > finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds > > Build Changeset > Revision 1818 committed by katem on 2007-04-04 12:47:28 removed > breakpoint M > /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb > Test Failures and Errors > Name: > test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) > Type: Failure Message: <1> expected but was <2>. > ./test/unit/question_set_element_test.rb:328 Name: > test_new_step_must_have_site_id(RegistrationWizardStepTest) Type: > Failure Message: <1> expected but was <2>. > ./test/unit/registration_wizard_step_test.rb:31 Name: > test_run(TalentPoolNotificationsTest) Type: Failure Message: <3> > expected but was <0>. ./test/unit/talent_pool_notifications_test.rb:60 > > > Any ideas why this may be? > > cheers > Levent > _______________________________________________ > 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/20070404/bfdc50cc/attachment.html
Levent Ali
2007-Apr-04 15:42 UTC
[Cruisecontrolrb-users] Reporting as fixed even though there are test failures
Cheers, Alex Verkhovsky mentioned this as well... I am just trying it now with ruby 1.8.5 (full rake takes about 45 minutes)... we were running 1.8.6 on the ci server... Thanks again Levent On 4/4/07, Jeremy Stell-Smith <jeremystellsmith at gmail.com> wrote:> Are you using Ruby 1.8.6? There is a bug with Ruby 1.8.6 that is causing > Test::Unit to return the incorrect exit code, and cruise not to fail. For > now, the fix is to go back to Ruby 1.8.4 or 1.8.5. We''re working on a > better workaround. > > On 4/4/07, Levent Ali <levent at leventali.com> wrote: > > > > Even though there are errors and failures in our tests Cruise Control > > is reporting the build is NOT broken and thus not emailing anybody... > > > > aspire_rails_12x build 1818 > > finished at 3:43 PM on 04 April 2007 taking 46 minutes and 17 seconds > > > > Build Changeset > > Revision 1818 committed by katem on 2007-04-04 12:47:28 removed > > breakpoint M > /aspire/branches/TRY-RAILS-1_2_X/app/models/talent_pool_notification.rb > > Test Failures and Errors > > Name: > test_question_element_should_only_occur_once_on_question_set(QuestionSetElementTest) > > Type: Failure Message: <1> expected but was <2>. > > ./test/unit/question_set_element_test.rb:328 Name: > > > test_new_step_must_have_site_id(RegistrationWizardStepTest) > Type: > > Failure Message: <1> expected but was <2>. > > ./test/unit/registration_wizard_step_test.rb:31 Name: > > test_run(TalentPoolNotificationsTest) Type: Failure > Message: <3> > > expected but was <0>. > ./test/unit/talent_pool_notifications_test.rb:60 > > > > > > Any ideas why this may be? > > > > cheers > > Levent > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > Cruisecontrolrb-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > >