I''ve recently updated to Rails 2.3.4 which I run under both Ruby 1.8.7p173 and 1.9.1p243. I also built both postgresql and mysql from source and installed these with a current sqlite3. The relevant adapter gems are current. I''m seeing errors and failures with the active record tests under ruby 1.9 for all 3 db''s that appear to have more to do with the test environment than the individual adapters or underlying db code. Summary lines for the different dbs are: sqlite3: 2072 tests, 6621 assertions, 1 failures, 86 errors, 0 pendings, 0 omissions, 0 notifications mysql: 2112 tests, 6688 assertions, 1 failures, 86 errors, 0 pendings, 0 omissions, 0 notifications postgresql: 2128 tests, 6825 assertions, 2 failures, 87 errors, 0 pendings, 0 omissions, 0 notifications The errors all report on undefined method. Three methods are identified with the greatest number being ''expects'' followed by ''with'' and ''stub''. These errors do not occur under Ruby 1.8 Any thoughts?
Those are moccha methods, it would seem like that gem isn''t being included or isn''t working properly On 2009-10-08, at 9:59, Rick <richard.t.lloyd@gmail.com> wrote:> > I''ve recently updated to Rails 2.3.4 which I run under both Ruby > 1.8.7p173 and 1.9.1p243. I also built both postgresql and mysql from > source and installed these with a current sqlite3. The relevant > adapter gems are current. > > I''m seeing errors and failures with the active record tests under ruby > 1.9 for all 3 db''s that appear to have more to do with the test > environment than the individual adapters or underlying db code. > > Summary lines for the different dbs are: > > sqlite3: > 2072 tests, 6621 assertions, 1 failures, 86 errors, 0 pendings, 0 > omissions, 0 notifications > > mysql: > 2112 tests, 6688 assertions, 1 failures, 86 errors, 0 pendings, 0 > omissions, 0 notifications > > postgresql: > 2128 tests, 6825 assertions, 2 failures, 87 errors, 0 pendings, 0 > omissions, 0 notifications > > The errors all report on undefined method. Three methods are > identified with the greatest number being ''expects'' followed by ''with'' > and ''stub''. These errors do not occur under Ruby 1.8 > > Any thoughts? > >
got that right - gem update mocha went 0.9.5 -> 0.9.8 test_mysql: 2112 tests, 6813 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications test_postgresql: 2128 tests, 6952 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications test_sqlite3: 2072 tests, 6746 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications thanks On Oct 8, 10:11 am, Mateo Murphy <mateo.mur...@gmail.com> wrote:> Those are moccha methods, it would seem like that gem isn''t being > included or isn''t working properly > > On 2009-10-08, at 9:59, Rick <richard.t.ll...@gmail.com> wrote: > > > > > I''ve recently updated to Rails 2.3.4 which I run under both Ruby > > 1.8.7p173 and 1.9.1p243. I also built both postgresql and mysql from > > source and installed these with a current sqlite3. The relevant > > adapter gems are current. > > > I''m seeing errors and failures with the active record tests under ruby > > 1.9 for all 3 db''s that appear to have more to do with the test > > environment than the individual adapters or underlying db code. > > > Summary lines for the different dbs are: > > > sqlite3: > > 2072 tests, 6621 assertions, 1 failures, 86 errors, 0 pendings, 0 > > omissions, 0 notifications > > > mysql: > > 2112 tests, 6688 assertions, 1 failures, 86 errors, 0 pendings, 0 > > omissions, 0 notifications > > > postgresql: > > 2128 tests, 6825 assertions, 2 failures, 87 errors, 0 pendings, 0 > > omissions, 0 notifications > > > The errors all report on undefined method. Three methods are > > identified with the greatest number being ''expects'' followed by ''with'' > > and ''stub''. These errors do not occur under Ruby 1.8 > > > Any thoughts?
Running geminstaller against ci/geminstaller.yml should install correct versions. Bundler is a great way to manage this, but not in use on 2-3 branch and not fully in use on master, so geminstaller is what the rails ci boxes still use. Sorry for top post, on iPhone On Thursday, October 8, 2009, Rick <richard.t.lloyd@gmail.com> wrote:> > got that right - gem update mocha went 0.9.5 -> 0.9.8 > > test_mysql: > 2112 tests, 6813 assertions, 0 failures, 0 errors, 0 pendings, 0 > omissions, 0 notifications > > test_postgresql: > 2128 tests, 6952 assertions, 0 failures, 0 errors, 0 pendings, 0 > omissions, 0 notifications > > test_sqlite3: > 2072 tests, 6746 assertions, 0 failures, 0 errors, 0 pendings, 0 > omissions, 0 notifications > > thanks > > On Oct 8, 10:11 am, Mateo Murphy <mateo.mur...@gmail.com> wrote: >> Those are moccha methods, it would seem like that gem isn''t being >> included or isn''t working properly >> >> On 2009-10-08, at 9:59, Rick <richard.t.ll...@gmail.com> wrote: >> >> >> >> > I''ve recently updated to Rails 2.3.4 which I run under both Ruby >> > 1.8.7p173 and 1.9.1p243. I also built both postgresql and mysql from >> > source and installed these with a current sqlite3. The relevant >> > adapter gems are current. >> >> > I''m seeing errors and failures with the active record tests under ruby >> > 1.9 for all 3 db''s that appear to have more to do with the test >> > environment than the individual adapters or underlying db code. >> >> > Summary lines for the different dbs are: >> >> > sqlite3: >> > 2072 tests, 6621 assertions, 1 failures, 86 errors, 0 pendings, 0 >> > omissions, 0 notifications >> >> > mysql: >> > 2112 tests, 6688 assertions, 1 failures, 86 errors, 0 pendings, 0 >> > omissions, 0 notifications >> >> > postgresql: >> > 2128 tests, 6825 assertions, 2 failures, 87 errors, 0 pendings, 0 >> > omissions, 0 notifications >> >> > The errors all report on undefined method. Three methods are >> > identified with the greatest number being ''expects'' followed by ''with'' >> > and ''stub''. These errors do not occur under Ruby 1.8 >> >> > Any thoughts? > > >
sqlite3 can''t run on ruby1.9. 2009/10/10 Chad Woolley <thewoolleyman@gmail.com>> > Running geminstaller against ci/geminstaller.yml should install > correct versions. Bundler is a great way to manage this, but not in > use on 2-3 branch and not fully in use on master, so geminstaller is > what the rails ci boxes still use. > > Sorry for top post, on iPhone > > On Thursday, October 8, 2009, Rick <richard.t.lloyd@gmail.com> wrote: > > > > got that right - gem update mocha went 0.9.5 -> 0.9.8 > > > > test_mysql: > > 2112 tests, 6813 assertions, 0 failures, 0 errors, 0 pendings, 0 > > omissions, 0 notifications > > > > test_postgresql: > > 2128 tests, 6952 assertions, 0 failures, 0 errors, 0 pendings, 0 > > omissions, 0 notifications > > > > test_sqlite3: > > 2072 tests, 6746 assertions, 0 failures, 0 errors, 0 pendings, 0 > > omissions, 0 notifications > > > > thanks > > > > On Oct 8, 10:11 am, Mateo Murphy <mateo.mur...@gmail.com> wrote: > >> Those are moccha methods, it would seem like that gem isn''t being > >> included or isn''t working properly > >> > >> On 2009-10-08, at 9:59, Rick <richard.t.ll...@gmail.com> wrote: > >> > >> > >> > >> > I''ve recently updated to Rails 2.3.4 which I run under both Ruby > >> > 1.8.7p173 and 1.9.1p243. I also built both postgresql and mysql from > >> > source and installed these with a current sqlite3. The relevant > >> > adapter gems are current. > >> > >> > I''m seeing errors and failures with the active record tests under ruby > >> > 1.9 for all 3 db''s that appear to have more to do with the test > >> > environment than the individual adapters or underlying db code. > >> > >> > Summary lines for the different dbs are: > >> > >> > sqlite3: > >> > 2072 tests, 6621 assertions, 1 failures, 86 errors, 0 pendings, 0 > >> > omissions, 0 notifications > >> > >> > mysql: > >> > 2112 tests, 6688 assertions, 1 failures, 86 errors, 0 pendings, 0 > >> > omissions, 0 notifications > >> > >> > postgresql: > >> > 2128 tests, 6825 assertions, 2 failures, 87 errors, 0 pendings, 0 > >> > omissions, 0 notifications > >> > >> > The errors all report on undefined method. Three methods are > >> > identified with the greatest number being ''expects'' followed by ''with'' > >> > and ''stub''. These errors do not occur under Ruby 1.8 > >> > >> > Any thoughts? > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On Fri, Oct 9, 2009 at 7:57 PM, Liping Huang <liping.huang2008@gmail.com> wrote:> sqlite3 can''t run on ruby1.9.It is running on 1.9 on the CI box, for the 2.3 branch: http://mri19.ci.rubyonrails.org:3333/builds/rails-2-3-stable-ruby-1-9-1 ...and master: http://mri19.ci.rubyonrails.org:3333/builds/rails-master-ruby-1-9-1 -- Chad
/sqliteTest 613 > script/about About your application''s environment Ruby version 1.9.1 (powerpc-darwin9.8.0) RubyGems version 1.3.5 Rack version 1.0 Rails version 2.3.4 Active Record version 2.3.4 Active Resource version 2.3.4 Action Mailer version 2.3.4 Active Support version 2.3.4 Application root /Users/rick/sqliteTest Environment development Database adapter sqlite3 Running in this environment passes all ActiveRecord "rake test- sqlite3" tests. On Oct 10, 6:50 pm, Chad Woolley <thewoolley...@gmail.com> wrote:> On Fri, Oct 9, 2009 at 7:57 PM, Liping Huang <liping.huang2...@gmail.com> wrote: > > sqlite3 can''t run on ruby1.9. > > It is running on 1.9 on the CI box, for the 2.3 branch: > > http://mri19.ci.rubyonrails.org:3333/builds/rails-2-3-stable-ruby-1-9-1 > > ...and master: > > http://mri19.ci.rubyonrails.org:3333/builds/rails-master-ruby-1-9-1 > > -- Chad