CruiseControl problem. Broken Pipe?

Hi Friends,

Just happened to catch this err in the CC log:

Build loop failed
BuilderError: Write failed: Broken pipe
./script/…/config/…/app/models/subversion.rb:98:in
execute_in_local_copy' ./script/../config/../lib/command_line.rb:86:incall’
./script/…/config/…/lib/command_line.rb:86:in e' ./script/../config/../lib/command_line.rb:84:inpopen’
./script/…/config/…/lib/command_line.rb:84:in e' ./script/../config/../lib/command_line.rb:71:inexecute’
./script/…/config/…/lib/command_line.rb:70:in chdir' ./script/../config/../lib/command_line.rb:70:inexecute’
./script/…/config/…/app/models/subversion.rb:89:in
execute_in_local_copy' ./script/../config/../app/models/subversion.rb:85:inchdir’
./script/…/config/…/app/models/subversion.rb:85:in
execute_in_local_copy' ./script/../config/../app/models/subversion.rb:57:inupdate’
./script/…/config/…/app/models/project.rb:277:in
update_project_to_revision' ./script/../config/../app/models/project.rb:293:inbuild’
./script/…/config/…/app/models/project.rb:209:in
build_if_necessary' ./script/../config/../app/models/polling_scheduler.rb:13:inrun’
./script/builder:79
./script/builder:78:in catch' ./script/builder:78 script/../config/../cruise:14:inload’
script/…/config/…/cruise:14:in builder' script/../config/../cruise:68:insend’
script/…/config/…/cruise:68
/usr/lib/ruby/1.8/fileutils.rb:121:in chdir' /usr/lib/ruby/1.8/fileutils.rb:121:incd’
script/…/config/…/cruise:67
[error] Write failed: Broken pipe

Any ideas as to what a broken pipe is referring to? Any help is
appreciated.

It means it’s writing to a file and then for some reason it was
interrupted.
Or it couldn’t write to the file in the first place. Check the
permissions.

On Jan 18, 2008 9:20 AM, mj [email protected] wrote:

./script/…/config/…/lib/command_line.rb:86:in e' ./script/../config/../app/models/subversion.rb:57:inupdate’
script/…/config/…/cruise:14:in `builder’


Ryan B.
http://www.frozenplague.net
Feel free to add me to MSN and/or GTalk as this email.

On Jan 17, 2008 3:58 PM, Ryan B. [email protected] wrote:

It means it’s writing to a file and then for some reason it was interrupted.

This coming from Subversion#update (which basically performs ‘svn up’
in work directory), it’s about socket connection from svn (Subversion
client) to the Subversion server.

Can you manually do ‘svn up’ in the work directory, using the same
user:group that the builder process runs under?


Alexey V.
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
RubyWorks [http://rubyworks.thoughtworks.com]

Not sure why this fixed it, but it turns out the svn URL had an IP
number in it. Once mj and I changed it to a normal domain name (using
“svn switch --relocate”) everything’s been working fine since (knock
knock). Thanks for the all helpful replies.

-Jason

On Jan 17, 3:06 pm, “Alexey V.” [email protected]