Hi again,

Invoking the build process from a local instance I see this:

dberger   9330 25625  0 16:10 ?        00:00:00 sh -c
echo /home/dberger/.cruise/projects/globe_village/work dberger$ ruby\ -e
\ \"require\ \'rubygems\'\ rescue\ nil\;\ require\ \'rake\'\;\ load\
\'/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake
\'\;\ ARGV\ \<\<\ \'--nosearch\'\ \<\<\ \'cc:build\'\;\
Rake.application.run\;\ ARGV.clear\"
>> /home/dberger/.cruise/projects/globe_village/build-28091f9.8/build.log && 
>> ruby -e "require 'rubygems' rescue nil; require 'rake'; load 
>> '/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake'; ARGV 
>> << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear" >> 
>> /home/dberger/.cruise/projects/globe_village/build-28091f9.8/build.log 2>&1

dberger   9331  9330 16 16:10 ?        00:00:09 ruby -e require
'rubygems' rescue nil; require 'rake'; load
'/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake';
ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear
dberger  22962     1  0 14:23 ?        00:00:01

ruby /home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/cruise build
globe_village

So, it looks like 2 processes there, 9330 and 9331. The latter has the
former as its parent pid.

I also tried switching to Passenger 2.x, but the result was the same.

In addition, I tried altering the :cruise task to just do "puts hello"
but it still seems to try to run the entire test suite. I slapped a
debug print statement in the cruise control source to make sure it was
picking up that there's a custom cruise task. It is.

Any ideas?

Regards,

Dan

On Mon, 2011-01-24 at 15:21 -0700, Daniel Berger wrote:
> BTW, I tried running this command (that showed up in ps -ef) from the
> command line manually in the work directory:
> 
> ruby -e "require 'rubygems' rescue nil; require 'rake'; load
> '/home/dberger/Downloads/Ruby/cruisecontrol-1.4.0/tasks/cc_build.rake';
> ARGV << '--nosearch' << 'cc:build'; Rake.application.run; ARGV.clear"
> 
> That worked fine.
> 
> Regards,
> 
> Dan
> 
> On Mon, 2011-01-24 at 15:03 -0700, Daniel Berger wrote:
> > Not that I can see. We do have multiple watchers setup that are pointing
> > at the same project but different branches.
> > 
> > Hm, is it possible we have projects setup pointing at the same branch by
> > mistake? Is there a way to tell? Would that cause it?
> > 
> > Regards,
> > 
> > Dan
> > 
> > On Mon, 2011-01-24 at 10:41 -0700, Alexey Verkhovsky wrote:
> > > It's not configured anywhere, moreover is not supposed to happen. But
> > > then, running the same build twice is not supposed to happen, either.
> > > ps -ef | grep build should tell you all you need.
> > > 
> > > On Mon, Jan 24, 2011 at 10:26 AM, Daniel Berger <[email protected]>
> > > wrote:
> > >         Hi,
> > >         
> > >         Can you help me determine if that's the case? Where is that
> > >         configured?
> > >         
> > >         Dan
> > >         
> > >         
> > >         On Mon, 2011-01-24 at 10:14 -0700, Alexey Verkhovsky wrote:
> > >         > Are you running two builder processes for the same project?
> > >         >
> > >         > On Mon, Jan 24, 2011 at 9:28 AM, Daniel Berger
> > >         <[email protected]>
> > >         > wrote:
> > >         >         Hi,
> > >         >
> > >         >         Ruby 1.8.7
> > >         >         Cruise Control 1.4.0
> > >         >         Passenger 3.0.2
> > >         >         git
> > >         >
> > >         >         Since upgrading to Passenger 3 we've noticed that
> > >         our Cruise
> > >         >         projects
> > >         >         try to run the test suite twice which is, in itself,
> > >         causing
> > >         >         some of our
> > >         >         tests to fail (on the second run).
> > >         >
> > >         >         Note that our tests pass (and only run once) on our
> > >         local
> > >         >         boxes, so it's
> > >         >         not some hidden fork call. Also, they pass if run
> > >         manually on
> > >         >         the server
> > >         >         hosting CC (and only run once). It's only the
> > >         automated
> > >         >         testing that
> > >         >         exhibits this behavior.
> > >         >
> > >         >         Any ideas?
> > >         >
> > >         >         Regards,
> > >         >
> > >         >         Dan
> > >         >
> > >         >         _______________________________________________
> > >         >         Cruisecontrolrb-users mailing list
> > >         >         [email protected]
> > >         >
> > >         http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
> > >         >
> > >         >
> > >         >
> > >         > --
> > >         > Alexey Verkhovsky
> > >         > http://alex-verkhovsky.blogspot.com/
> > >         > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
> > >         >
> > >         > _______________________________________________
> > >         > Cruisecontrolrb-users mailing list
> > >         > [email protected]
> > >         > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
> > >         
> > >         
> > >         _______________________________________________
> > >         Cruisecontrolrb-users mailing list
> > >         [email protected]
> > >         http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
> > >         
> > > 
> > > 
> > > 
> > > -- 
> > > Alexey Verkhovsky
> > > http://alex-verkhovsky.blogspot.com/
> > > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
> > > 
> > > _______________________________________________
> > > Cruisecontrolrb-users mailing list
> > > [email protected]
> > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
> > 
> > 
> > _______________________________________________
> > Cruisecontrolrb-users mailing list
> > [email protected]
> > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
> 
> 
> _______________________________________________
> Cruisecontrolrb-users mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users


_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Reply via email to