#1398: "rake spec:ci" fails more specs. ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: critical | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- Comment(by mrada@…): Ok, with some modifications to the specs I get this: {{{ Finished in 711.644263 seconds 3337 files, 14730 examples, 57553 expectations, 0 failures, 8 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/macruby.msp...] }}} The modification is this: {{{ diff --git a/spec/macruby/library/rake/compiletask_spec.rb b/spec/macruby/library/rake/compiletask_spec.rb index f2dbe44..4b6b37e 100644 --- a/spec/macruby/library/rake/compiletask_spec.rb +++ b/spec/macruby/library/rake/compiletask_spec.rb @@ -1,7 +1,13 @@ require File.expand_path('../../../spec_helper', __FILE__) -require 'rake/compiletask' +# require 'rake/compiletask' require 'stringio' +# it could already be loaded by rubygems or others +unless MacRuby.const_defined?(:Compiler) + load File.join(RbConfig::CONFIG['bindir'], 'macrubyc') +end + + module CompileTaskSpecHelper include FileUtils }}} So I suspect the problem is because the specs would normally load rake into the same process. Since I can still load macrubyc without any extra problems I dont think it macrubyc is causing the test failures. It might be that rake is doing something to the run time that causes the other tests to fail but I am not sure. I think the CompileTask itself is self- contained and should not being causing the problem. I will have to look into more after some sleep. -- Ticket URL: <http://www.macruby.org/trac/ticket/1398#comment:9> MacRuby <http://macruby.org/>