> Is there any other logging I can enable? Hi Mike, I just created a patch that will help you debug this problem by logging some information in /tmp/logfile. The patch is at:
http://bugzilla.mkgnu.net/show_bug.cgi?id=1093#c5 Can you try it and report back what you see ? > One other symptom is that a perl process is running at 99% cpu > utilization when the commit failure occurs. The svn commit eventually > times out with "no response from server". Do you have an estimate on how long you have waited ? My gut feeling is that either you have a slow machine and it takes a while for Scmbug to run 'svnlook' to see what changed in history. Or Subversion hangs due to Scmbug issuing 'svnlook' and waiting for a very long time which may be raising racing issues in Subversion.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
