1. 17 1月, 2012 2 次提交
  2. 07 1月, 2012 1 次提交
  3. 29 12月, 2011 1 次提交
  4. 28 12月, 2011 1 次提交
  5. 22 12月, 2011 1 次提交
  6. 21 12月, 2011 2 次提交
  7. 18 12月, 2011 1 次提交
  8. 16 12月, 2011 2 次提交
  9. 15 12月, 2011 2 次提交
  10. 10 12月, 2011 1 次提交
  11. 09 12月, 2011 1 次提交
  12. 01 12月, 2011 1 次提交
  13. 30 11月, 2011 1 次提交
  14. 28 11月, 2011 1 次提交
  15. 25 11月, 2011 1 次提交
  16. 04 11月, 2011 1 次提交
  17. 03 11月, 2011 3 次提交
  18. 28 9月, 2011 1 次提交
  19. 26 9月, 2011 3 次提交
  20. 07 9月, 2011 1 次提交
  21. 06 9月, 2011 4 次提交
  22. 29 8月, 2011 1 次提交
  23. 15 8月, 2011 1 次提交
  24. 13 8月, 2011 1 次提交
    • J
      Work around for lolruby bug. (Read on for explanation.) · 34689c40
      Jon Leighton 提交于
      We were experiencing CI test failures, for example:
      
      * 3-1-stable: http://travis-ci.org/#!/rails/rails/builds/79473/L407
      * master: http://travis-ci.org/#!/rails/rails/builds/79507/L80
      
      These failures only happened on 1.8.7-p352, and we were only able to
      reproduce on the Travis CI VM worker. We even tried creating a new 32
      bit Ubuntu VM and running the tests on that, and it all worked fine.
      
      After some epic trial and error, we discovered that replacing the
      following:
      
        fuu = Marshal.load(Marshal.dump(fuu))
      
      with:
      
        marshalled = Marshal.dump(fuu)
        fuu = Marshal.load(marshalled)
      
      seemed to prevent the failure.
      
      We have NO IDEA why this is. If anyone has some great insight to
      contribute then that is welcome. Otherwise, hopefully this will just
      help us get the CI green again.
      
      Many thanks to @joshk for help with sorting this out.
      34689c40
  25. 06 8月, 2011 1 次提交
  26. 19 7月, 2011 1 次提交
  27. 12 7月, 2011 1 次提交
  28. 09 7月, 2011 2 次提交