On Mon, Sep 24, 2012 at 11:15 PM, Ben Reser <b...@reser.org> wrote: > On Mon, Sep 24, 2012 at 7:38 PM, Hyrum K Wright <hy...@hyrumwright.org> wrote: >> The svn-x64-ubuntu-gcc bot currently lives in my basement, and was >> recently upgraded to the latest Ubuntu beta release, which bumped a >> number of dependency versions. The biggest issue with the bindings is >> the bump to Ruby 1.9 which we explicitly don't support because the >> tests are not currently compatible with it. It seems that Ruby 1.9 is >> the Next Big Thing, and 1.8 is soon to unsupported, so a number of >> distros are moving to it as the default. >> >> I've spent the evening digging into what it would take to support Ruby >> 1.9, but my Ruby-fu is so weak that it'll be more than an evening for >> me to actually make progress on the issue. I invite more capable >> hands to join in the effort. > > Yeah I noticed the Ruby failure. If the machine running this buildbot > is being shared by some other use for you maybe we should split this > off. I have a KVM setup dedicated for Subversion work and would be > happy to host this slave as a dedicated guest. This would allow us to > have upgrades only when we wanted them for the specific build slave. > > Obviously the work to move to 1.9 would still need to be done, but > there's really not much value in having our build bot fail on > something we're not expecting to work.
For the time being, the Ruby build step and tests have been commented out of the relevant scripts. I think there is value in running a bot on a stock (albeit currently beta) install of a popular Linux distribution. We don't control our users' machines, and pretty soon many of them will be upgrading to the latest Ubuntu. A not-insignificant-number of those people will discover their Subversion Ruby scripts don't work anymore. This is unfortunate, and the sooner we can find these problems, the better. Running a bot in this type of environment is one way to do so. (Plus, I haven't committed a line of code in 3 months: I have to do _something_ to feel more useful than just kibitzing on dev@. :) ) You are, of course, welcome to run yet another bot with its own configuration, but I recommend we still use this one. -Hyrum
