Does anybody know what exactly goes wrong? Maybe it could work if we use port forwarding or stunnel or something to route the traffic to the dynamic clients over some server with a static IP?
Here's my last svn failed log. It was on the native machine, and I just discovered that the two slaves on the VMWare virtual machine have been not responding for a couple of days, so it cannot be a matter of simultaneous access on the same machine. I'm going to try to restart them.
Could the svn server be sensitive to too many clients hitting the same repository at the same time? Perhaps it would help to introduce a delay between triggering one slave and the next, or if that is not possible adding a sleep of a random time on the slaves before the svn update.
-- sidney
The log:
starting svn operation
command '['svn', 'update', '--revision', '122631']' in dir /b/home/buildbot/slaves/sidney-fedora3/trunk-sidney-fedora3/build (timeout 1200 secs)
svn: PROPFIND request failed on '/repos/asf/spamassassin/trunk'
svn: PROPFIND of '/repos/asf/spamassassin/trunk': Could not read status line: connection was closed by server. (http://svn.apache.org)
update failed, clobbering and trying again
command '['rm', '-rf', '/b/home/buildbot/slaves/sidney-fedora3/trunk-sidney-fedora3/build']' in dir /b/home/buildbot/slaves/sidney-fedora3/trunk-sidney-fedora3 (timeout 1200 secs)
now retrying VC operation
command '['svn', 'checkout', '--revision', '122631', 'http://svn.apache.org/repos/asf/spamassassin/trunk', 'build']' in dir /b/home/buildbot/slaves/sidney-fedora3/trunk-sidney-fedora3 (timeout 1200 secs)
svn: PROPFIND request failed on '/repos/asf/spamassassin/trunk'
svn: PROPFIND of '/repos/asf/spamassassin/trunk': Could not read status line: connection was closed by server. (http://svn.apache.org)
program finished with exit code 1
