Hey Nick, I figured it out! Travis rebases your commits on the current master branch, while i was not doing so. Rebasing the changes onto the master branch and then running tests gave me the same results as Travis got.
I'm still confused why the tests *would* pass in certain cases in Travis - it seems a weird inconsistency. I was able to figure out and fix the failing tests now. Hopefully this helps you too! Cheers, David On Friday, 6 June 2014 15:17:18 UTC+3, Nick Sutterer wrote: > > Hi Dave, > > not exactly the same issue, but I also have all tests passing locally and > one failing test on Travis, with the "ar" (= activerecord) test suite. I'll > look into it tomorrow. > > > Nick > > On Friday, June 6, 2014 12:14:44 AM UTC+10, David V. wrote: >> >> I've recently updated some Rails code which passed all the tests when I >> ran them locally using the Rails dev box. >> >> However, the tests fail in certain situations in Travis. I can't seem to >> reproduce these situations, and I've been unable to fix the bug. Does >> anyone know how I can replicate that environment and/or reproduce these >> failing tests? It appears to happen whenever the GEM env variable contains >> "ar" (activerecord?), but I don't know what that reflects on. >> >> - PR request: https://github.com/rails/rails/pull/15322 >> - Failing travis build: https://travis-ci.org/rails/rails/builds/26198080 >> >> Any help appreciated! >> > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
