Em 30-11-2012 13:22, Gary Weaver escreveu:
So, it is not that quick either to get started contributing to
Rails (it may require an hour or two just to get the tests passing).
Rodrigo, did you try the VM method? https://github.com/rails/rails-dev-box
Thanks for the pointer, Gary but I avoided it on purpose. 8GB is not
enough anymore for my dev machine with so many processes running here
(Grails + Rails + GlassFish with Java app + Solr + Redis + PG 9.1 + PG
9.2 + MySql + VirtualBox to test IE + Amarok, etc) I really want to
avoid yet another VM :)
But it seems one problem is that I was using the falcon patch to Ruby
and the other problem is that I had a few options in ~/.railsrc that
prevented the railties tests to pass. All of them have already been
fixed and I can now go green with Rails tests. So, next time I find some
free time I'll be able to give it a try:
https://github.com/rails/rails/issues/8384
https://github.com/rails/rails/issues/8386
Thanks to Carlos, Rafael and Steve for helping me out in the process :)
Man, those tests in railties are painfully slow! :( Luckily I won't need
to change railties but only activerecord I hope :)
So that I can focus on the changes themselves, what is the recommended
way of manually testing my changes while pointing my project to use AR
under my Rails clone?
gem 'activerecord', path: '~/rails-clone/activerecord' # should this be
enough? - recall that I don't use Rails for this database management
project, only standalone_migrations gem.
Cheers,
Rodrigo.
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
