I have temporary resources (working on that CI thing for gem-testers... have a beefy box that's dedicated to it, but the system isn't finished yet) that we could use for the meantime.
IOW, if someone has a more permanent solution, great, but if not, I can help. -Erik On May 4, 2011, at 11:51 AM, Ryan Davis wrote: > > On May 3, 2011, at 18:23 , Luis Lavena wrote: > >> Saw this commit: >> https://github.com/rubygems/rubygems/commit/aa4bd18e93d7de7124d12f9c185be7474a55bc4d >> >> I can say things are not that green on Windows: >> >> ruby 1.9.2p180 (2011-02-18) [i386-mingw32] >> 844 tests, 1823 assertions, 0 failures, 338 errors, 17 skips >> >> Don't have the time to check tonight, so hope you guys are not >> thinking on doing a release without giving me enough heads up for a >> proper check. > > My fault. I took a shortcut I shouldn't have taken. I'm now getting: > >> 821 tests, 2644 assertions, 1 failures, 5 errors, 21 skips > > the 1/5 are all related to configure/make and presumably pass when I have a > proper development environment. I'm a windows newb and that's currently > beyond me. Frankly, I'm amazed I got this far (I'm even running autotest on > cmd inside of emacs!). I've pushed a fix. > > Related: Do we have access to any resources to run a CI on windows? I really > don't want to have to fire up vmware often. > > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
