Karl Heinz Marbaise <khmarba...@gmx.de> writes: > Hi, > > so after i did an svn up i got this: > > Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn up > Updating '.': > G src/it/mexec-100/pom.xml > G src/it/mexec-105/pom.xml > > more or less expected.... > >> furthermore i have recodnized that the local files are currently in the >> state of modified: >> >> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn st >> M src/it/mexec-100/pom.xml >> M src/it/mexec-105/pom.xml >> >>> i observed a strange thing during a checkin process running where i got >>> the following messages: >>> >>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff >>> Sending src/it/mexec-100/pom.xml >>> Sending src/it/mexec-105/pom.xml >>> Transmitting file data .. >>> Committed revision 19310. >>> svn: E120108: Commit failed (details follow): >>> svn: E120108: Error running context: The server unexpectedly closed the >>> connection. >>> svn: E120108: Additional errors: >>> svn: E120108: Error running context: The server unexpectedly closed the >>> connection.
E120108 is unknown on my Linux box: $ ../src/tools/dev/which-error.py E120108 00120108 *** UNKNOWN ERROR CODE *** The client recognises SVN_ERR_REPOS_POST_COMMIT_HOOK_FAILED (165007) as a failed post-commit so the unknown E120108 meant the client didn't do post-commit processing so the committed files showed up as uncommitted. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
