Kristis, There was no data written to /tmp/logfile.
I deployed your patch to /usr/share/scmbug/lib/Scmbug/Glue/Subversion.pm The Red Hat patch utility didn't apply the last chunk of changes. I did that by hand. I've attached the patched Subversion.pm so you can verify that I made the changes correctly. The TortoiseSVN commit dialog window takes over 40 minutes before it times out. The test repository I am using has a single file in the repository and is at revision 44. The test file is 65 bytes. The server running Subversion is an Intel P4 2.8GHz, 1024KB cache, 2GB RAM (Linux reports 5605 bogomips). Regards, Mike -----Original Message----- From: Kristis Makris [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 16, 2008 1:21 PM To: Brown, Mike Cc: 'Oliver Schäfer'; '[email protected]' Subject: RE: [scmbug-users] very large commit comments break scmbug + bugz illa > 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.
Subversion.pm
Description: Binary data
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
