Summary: CI is green on 1.8.7, failing on 1.9.1 and 1.9.2. Notifications to dev list can now be enabled per-interpreter (and are currently only enabled for 1.8.7). All the 1.9.x problems are locally reproducible for me, AFAIK there are no issues with the CI environment, and let me know if you believe otherwise.
Details: I merged the CI improvements to master: https://github.com/rubygems/rubygems/commit/fda095d32a56f0c595b12d361885d9fad29780d8 "Continuous Integration config enhancements and wrapper script. Support for multiple interpeters via RVM, better reproducibility of failed builds via environment auto-setup in wrapper script, and granular control over failure notifications emails for selected interpreters" Responses to your prior feedback inline below... On Tue, Dec 21, 2010 at 2:16 PM, Ryan Davis <ryand-r...@zenspider.com> wrote: > On Dec 13, 2010, at 22:52 , Chad Woolley wrote: >>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p302 > This is the latest version of 1.8.7 and runs clean. Yep, it does. Yay! > I dunno if you have control over this, but not having good titles on the HTML > page makes distinguishing tabs a PITA. Only if I hack CCRB, which I don't want to. I'd rather put effort into moving everything to Hudson, which is a whole other side project. For now, I'd recommend http://ccmenu.sourceforge.net/ if you want to easily monitor build status. > p430 is the latest release on 1.9.1. Done: http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430 ...but it has the same problem: > This fails: > >> rake aborted! >> no such file to load -- hoe >> >> /home/pivotal/.cruise/projects/RubyGems-1_9_1-p429/work/Rakefile:8 >> :in `require' > > So, environmental problem here... No, you can see that Hoe was just installed successfully, but then Rake can't find it. It's probably something related to the immediately preceding errors about gem_prelude and the frozen load path. I tried hacking the wrapper script to run rake in a subshell (thinking it would then know the gems WERE actually installed), but this didn't make any difference. It is also reproducible locally if you install RVM and run the following (let me know if it isn't locally reproducible for you): ./ci_build.sh '1.9.1-p...@rubygems' > p0 is the latest release for 1.9.2. Done: http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0 The 1.9.2-p0 build is failing with "NoMethodError: undefined method `dump' for Psych:Module", which is also locally reproducible: ./ci_build.sh '1.9.2...@rubygems' > Why is it building ruby on every run? It isn't, only if the specified RVM interpre...@rubygems isn't already installed. It IS installing the gems every run, but that's an intentional hack because you still haven't told me how to make hoe not use sudo for "check_extra_deps". Let me know Thanks, -- Chad _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
