Due to new svnkit in Hudson, we've stucked with update failures on some node
(debian).
It looks like this:
======================
started
Building remotely on deb4 APS catalog
Updating svn://ofsvn.plesk.ru:3693/apscatalog/trunk
ERROR: Failed to update svn://ofsvn.plesk.ru:3693/apscatalog/trunk
org.tmatesoft.svn.core.SVNException: svn: Network connection closed unexpectedly
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:55)
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:40)
at
org.tmatesoft.svn.core.internal.io.svn.SVNReader.readChar(SVNReader.java:559)
at
org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:293)
at
org.tmatesoft.svn.core.internal.io.svn.SVNConnection.handshake(SVNConnection.java:103)
at
org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:62)
at
org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:974)
at
org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getDatedRevision(SVNRepositoryImpl.java:159)
at
org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:346)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:159)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:382)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:354)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1093)
at hudson.remoting.UserRequest.perform(UserRequest.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:23)
at hudson.remoting.Request$2.run(Request.java:200)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
======================

however, executing the same 'svn up' command with shell on the node works well.
I have no idea about the reasons for now, cos other nodes does not fail (with
same SVN version there). I had to downgrade Hudson to 1.201 - everything goes
fine.

More info:

SVN version:
===========
>svn --version
svn, version 1.4.2 (r22196)
compiled Nov 10 2006, 17:39:50
===========

Hudson version: 1.204