I noticed that my unit tests started failing after doing an svn up today, so I tried to zero in on the revision: 3713: fail 3700: pass 3710: fail 3705: pass 3706: pass 3708: fail 3707: fail 3706 is good, 3707 kills them. I get this weirdness at the console: (where plan is SpendingPlan.find(:first))>> plan.valid?=> true>> plan.save!ActiveRecord::RecordNotSaved: ActiveRecord::RecordNotSaved from ./script/../config/../config/../vendor/rails/activerecord/lib/active_record/base.rb:1297:in `save_without_validation!'' from ./script/../config/../config/../vendor/rails/activerecord/lib/active_record/validations.rb:734:in `save!'' from (irb):8>>There are no before_saves or "validates" on this model, and no database constraints. No errors in the test.log or development.log output.
Wilson Bilkovich wrote:> 3706 is good, 3707 kills them.I''m also getting something odd after 3707, don''t know exactly what it is yet.
Michael Schoen wrote:> Wilson Bilkovich wrote: >> 3706 is good, 3707 kills them. > > I''m also getting something odd after 3707, don''t know exactly what it is > yet.Ok, found my problem, not sure if it''s the same as yours -- locking wasn''t returning true if the update was successful. Patch submitted: http://dev.rubyonrails.org/ticket/4015
> Ok, found my problem, not sure if it''s the same as yours -- locking > wasn''t returning true if the update was successful. > > Patch submitted: > > http://dev.rubyonrails.org/ticket/4015 >And applied. -- Cheers Koz
On 3/1/06, Michael Schoen <schoenm@earthlink.net> wrote:> Michael Schoen wrote: > > Wilson Bilkovich wrote: > >> 3706 is good, 3707 kills them. > > > > I''m also getting something odd after 3707, don''t know exactly what it is > > yet. > > Ok, found my problem, not sure if it''s the same as yours -- locking > wasn''t returning true if the update was successful. > > Patch submitted: > > http://dev.rubyonrails.org/ticket/4015 >Nice work. This fixed it for me as well.