Help needed with failed tests while running Rails test suite

rubyonrails-core
#1

While trying to run the Rails test suite, I did:

- git clone rails
- gem install bundler
- gem bundle
- followed instructions for setting up mysql databases from Rails guides included on repository
- run "rake test"

I miss these instructions on a RUNNING_TEST_SUITE.README. Can I submit such a file (read: would it be updated when this process changes?)

Then, I got these failed tests:

(in /home/rodrigo/src/git/rails/activesupport)
...
1) Failure:
test_local_time(TimeExtCalculationsTest)
    [./test/core_ext/time_ext_test.rb:600:in `test_local_time'
     /home/rodrigo/src/git/rails/vendor/gems/gems/mocha-0.9.8/lib/mocha/integration/test_unit/ruby_version_186_and_above.rb:19:in `__send__'
     /home/rodrigo/src/git/rails/vendor/gems/gems/mocha-0.9.8/lib/mocha/integration/test_unit/ruby_version_186_and_above.rb:19:in `run']: <Mon Feb 21 17:44:30 -0300 2039> expected but was

<Mon, 21 Feb 2039 17:44:30 -0200>.

  2) Failure:
test_time_with_datetime_fallback(TimeExtCalculationsTest)
    [./test/core_ext/time_ext_test.rb:578:in `test_time_with_datetime_fallback'
     /home/rodrigo/src/git/rails/vendor/gems/gems/mocha-0.9.8/lib/mocha/integration/test_unit/ruby_version_186_and_above.rb:19:in `__send__'
     /home/rodrigo/src/git/rails/vendor/gems/gems/mocha-0.9.8/lib/mocha/integration/test_unit/ruby_version_186_and_above.rb:19:in `run']: <Mon Feb 21 17:44:30 -0300 2039> expected but was

<Mon, 21 Feb 2039 17:44:30 -0200>.

(in /home/rodrigo/src/git/rails/actionpack)
...
2554 tests, 11749 assertions, 0 failures, 0 errors

Pending Cases:
test_response_cache_control_from_rackish_app at ./test/dispatch/response_test.rb, line 190
test_response_cache_control_from_railsish_app at ./test/dispatch/response_test.rb, line 171
test_response_charset_and_content_type_from_rackish_app at ./test/dispatch/response_test.rb, line 226
test_response_charset_and_content_type_from_railsish_app at ./test/dispatch/response_test.rb, line 208
test_file_stream at ./test/controller/send_file_test.rb, line 54 Loaded suite /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader

Started

E...................................................................

Finished in 78.729453 seconds.

  1) Error:
test_log_with_active_record(ARLoggingTest):
NoMethodError: undefined method `generate' for nil:NilClass
    /home/rodrigo/src/git/rails/actionpack/lib/action_dispatch/routing/route_set.rb:381:in `generate'
    /home/rodrigo/src/git/rails/actionpack/lib/action_dispatch/routing/route_set.rb:328:in `generate_extras'
    /home/rodrigo/src/git/rails/actionpack/lib/action_dispatch/routing/route_set.rb:324:in `extra_keys'
    /home/rodrigo/src/git/rails/actionpack/lib/action_controller/test_case.rb:23:in `assign_parameters'
    /home/rodrigo/src/git/rails/actionpack/lib/action_controller/test_case.rb:240:in `process'
    /home/rodrigo/src/git/rails/actionpack/lib/action_controller/test_case.rb:188:in `get' ./test/activerecord/controller_runtime_test.rb:26:in `test_log_with_active_record'
    /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `__send__'
    /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `run'
    /home/rodrigo/src/git/rails/activesupport/lib/active_support/callbacks.rb:411:in `_run_setup_callbacks'
    /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:62:in `run'

(in /home/rodrigo/src/git/rails/activerecord)
...
1) Failure:
test_validate_uniqueness(UniquenessValidationTest)
    [./test/cases/validations/uniqueness_validation_test.rb:54:in `test_validate_uniqueness'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `__send__'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `run'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/callbacks.rb:416:in `_run_setup_callbacks'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:62:in `run']: Shouldn't be valid.

<false> is not true.

  2) Failure:
test_validate_uniqueness_with_limit_and_utf8(UniquenessValidationTest)
    [./test/cases/validations/uniqueness_validation_test.rb:247:in `test_validate_uniqueness_with_limit_and_utf8'
     /home/rodrigo/src/git/rails/activerecord/lib/active_record/test_case.rb:57:in `with_kcode' ./test/cases/validations/uniqueness_validation_test.rb:242:in `test_validate_uniqueness_with_limit_and_utf8'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `__send__'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:64:in `run'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/callbacks.rb:416:in `_run_setup_callbacks'
     /home/rodrigo/src/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:62:in `run']: Created an event whose title, with limit taken into account, is not unique. <false> is not true.

... postgresql test errors ignored since I didn't setup postgresql database ...

(in /home/rodrigo/src/git/rails/railties)
/home/rodrigo/src/git/rails/activesupport/lib/active_support/dependencies.rb:456:in `load_missing_constant': uninitialized constant ActiveRecord::Rails::Plugin (NameError)
        from /home/rodrigo/src/git/rails/activesupport/lib/active_support/dependencies.rb:91:in `const_missing'
        from /home/rodrigo/src/git/rails/activerecord/lib/active_record/rails.rb:9
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from /home/rodrigo/src/git/rails/activesupport/lib/active_support/dependencies.rb:167:in `require'
        from /home/rodrigo/src/git/rails/activesupport/lib/active_support/dependencies.rb:537:in `new_constants_in'
        from /home/rodrigo/src/git/rails/activesupport/lib/active_support/dependencies.rb:167:in `require'
        from /home/rodrigo/src/git/rails/railties/lib/rails.rb:6
        from /home/rodrigo/src/git/rails/railties/lib/rails.rb:3:in `each'
        from /home/rodrigo/src/git/rails/railties/lib/rails.rb:3
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from ./test/abstract_unit.rb:23
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from test/initializable_test.rb:1

Could someone point me what am I missing?

I would like to try to use my tomorrow's (actually today already) morning to try to give the validations :full_message option a try, since I'll have some time to invest on it...

Thanks in advance,

Rodrigo.

#2

I’m not entirely sure that master would be 100% passing, since it’s in a state of flux now in the build up to the Rails 3 beta.

#3

And indeed, if you check http://ci.rubyonrails.org/ you can see that Rails builds are pretty hit-or-miss on master right now.

Mike

#4

Yeah. The Core team has been bugging me to send campfire
notifications so they are more aware of breakages, but we're still
(slowly) trying to get the campfire notifier plugin for CCRB working.
Hope to hack it some New Year's Eve.

I also notice the 1.9 build server is down, I'll look into that (as
soon as my son is off my laptop where my ssh key is).

-- Chad

#5

But looking at ci log, it seems that there are some bugs with timezones:

http://mri187.ci.rubyonrails.org:3333/builds/rails-master-ruby-1-8-7/16f1a2b

ActiveSupport builds with no error, while I get 2 failures here. I've noted this warning in my log, but I have no idea what it means:
./test/../lib/active_support/core_ext/string/output_safety.rb:40: warning: discarding old concat

These are the failed tests that seem to be buggy (I'm probably on a different timezone of ci's, i.e Brazilian timezone):

<Mon Feb 21 17:44:30 -0300 2039> expected but was
<Mon, 21 Feb 2039 17:44:30 -0200>.

<Mon Feb 21 17:44:30 -0300 2039> expected but was
<Mon, 21 Feb 2039 17:44:30 -0200>.

Does it happen with someone else?

Note: I'm skipping memcached backd store tests once I don't have it installed.

Thanks,

Rodrigo.

Mike Gunderloy escreveu:

#6

Any chance this is related?

http://groups.google.com/group/rubyonrails-talk/browse_frm/thread/5379ac328f6d713f

I've got no idea what the DST situation in Brazil is, but that thread jumped out as being possibly related.

--Matt Jones

#7

Matt Jones escreveu:

  

These are the failed tests that seem to be buggy (I'm probably on a
different timezone of ci's, i.e Brazilian timezone):

<Mon Feb 21 17:44:30 -0300 2039> expected but was
<Mon, 21 Feb 2039 17:44:30 -0200>.

<Mon Feb 21 17:44:30 -0300 2039> expected but was
<Mon, 21 Feb 2039 17:44:30 -0200>.

Does it happen with someone else?

Any chance this is related?

http://groups.google.com/group/rubyonrails-talk/browse_frm/thread/5379ac328f6d713f

I've got no idea what the DST situation in Brazil is, but that thread jumped out as being possibly related.
  

Hi Matt,

I've tried updating my debian sid again (tzdata and tz-brasil), installing tzinfo gem but the failures persist (I think that is good, since it is consistent with Rails not requiring tzinfo gem).

Any other idea?

Thanks once more,

Rodrigo.

P.S: Timezone seems to be working well here, as always...