[Rubygems-developers] CI Status (was: RubyGemsGitHub build 1e71d86 failed)

Ryan Davis ryand-ruby at zenspider.com
Tue Dec 21 16:16:20 EST 2010

On Dec 13, 2010, at 22:52 , Chad Woolley wrote:

> On Mon, Dec 13, 2010 at 9:17 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
>> I've got a working pass at a dynamic multi-interpreter build here (and
>> it's green under 1.8.7):
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p302

This is the latest version of 1.8.7 and runs clean.

I dunno if you have control over this, but not having good titles on the HTML page makes distinguishing tabs a PITA.

> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p429

p430 is the latest release on 1.9.1.

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...

> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-rc2

p0 is the latest release for 1.9.2.

Why is it building ruby on every run?

This one has failures, but they're not visible in the CI. I suspect it is just truncating because of the annoying YAML warning on a billion lines. If I click on the raw log they're all:

> /home/pivotal/.rvm/rubies/ruby-1.9.2-rc2/lib/ruby/1.9.1/rubygems.rb:335:in `bin_path': can't find executable rake for rake-0.8.7 (Gem::Exception)

So I suspect something environmental still.

More information about the Rubygems-developers mailing list