On Wed, Feb 25, 2009 at 7:21 PM, Jaydeep Ghurye <[email protected]>wrote:
> Hi Kristis, > I did as you instructed, and this time I got a lot more > information, using which I was able to debug the problem to quite some > extent on my own. First I will print the error messages that appeared in the > scmbug_glue.log file, and then I will put forward my conclusions about what > appears to be broken: > > Log File: > ------------ > > 2009/02/25 02:22:10 Scmbug WARN> Glue.pm:109:Scmbug::Glue::Glue::process - > --------------------------------------------------------- > 2009/02/25 02:22:10 Scmbug INFO> Glue.pm:110:Scmbug::Glue::Glue::process - > Read configuration file 'C:\Repos\repo1/hooks/etc/scmbug/glue.conf' > 2009/02/25 02:22:10 Scmbug INFO> > Glue.pm:206:Scmbug::Glue::Glue::check_configuration - Checking configuration > 2009/02/25 02:22:13 Scmbug INFO> > Subversion.pm:100:Scmbug::Glue::Subversion::detect_version - Detected > Subversion version > 2009/02/25 02:22:13 Scmbug WARN> > SCM.pm:307:Scmbug::Glue::SCM::prepare_activity - Preparing for VERIFICATION > 2009/02/25 02:22:13 Scmbug INFO> > Subversion.pm:199:Scmbug::Glue::Subversion::prepare_activity_verify_or_commit > - Calling 'svnlook.exe info' to collect activity information > 2009/02/25 02:22:17 Scmbug INFO> > Subversion.pm:215:Scmbug::Glue::Subversion::prepare_activity_verify_or_commit > - Reading the log message > 2009/02/25 02:22:17 Scmbug INFO> > Subversion.pm:236:Scmbug::Glue::Subversion::prepare_activity_verify_or_commit > - This is a commit activity, and we must find the new version number using > transaction number '4-k' > 2009/02/25 02:22:17 Scmbug INFO> > Subversion.pm:237:Scmbug::Glue::Subversion::prepare_activity_verify_or_commit > - Calling 'svnlook.exe youngest' to find the current repository revision > 2009/02/25 02:22:20 Scmbug INFO> > Subversion.pm:249:Scmbug::Glue::Subversion::prepare_activity_verify_or_commit > - Calling 'svnlook.exe changed' to find the list of affected files > 2009/02/25 02:22:23 Scmbug DEBUG> > SCM.pm:339:Scmbug::Glue::SCM::prepare_final_log_message - > presence_of_bug_ids is 'required'. > 2009/02/25 02:22:23 Scmbug INFO> > SCM.pm:347:Scmbug::Glue::SCM::prepare_final_log_message - Searching for > resolution bug ids > 2009/02/25 02:22:23 Scmbug INFO> > SCM.pm:476:Scmbug::Glue::SCM::prepare_final_log_message - Searching for log > bug ids > 2009/02/25 02:22:23 Scmbug DEBUG> > SCM.pm:511:Scmbug::Glue::SCM::prepare_final_log_message - The log message > with the resolution removed is '' > 2009/02/25 02:22:23 Scmbug ERROR> > SCM.pm:528:Scmbug::Glue::SCM::prepare_final_log_message - > ******************************************* > ** > ** > ** Scmbug error 3: No list of bug ids was found that matches the > log_bugid_regex '^\s*bug\s*([\d|\s|,|#]*?):' and log_bugid_split_regex > ',\s?#|\s?#|,|\s+' in the log message ''. > ** > ** > ******************************************* > > I used the information above to try and debug the problem, and (I may be > wrong here, my Perl is not good at all) I think that line 200 of the file > <REPOSITORY>/hooks/lib/scmbug/Scmbug/Glue/Subversion.pm, namely > > open ( SVNLOOK_INFO, "svnlook.exe info " . $svn_tools_argument . " $svn_txn > $svn_repository |" ) > > is not generating the desired output. > > I tried running the command in this line manually, like this: > > svnlook info -t 4-k C:/Repos/Repo1 > > and got the output: > > svnlook: No such transaction > > The svnlook command works fine without the "-t" option, like this: > > svnlook info C:/Repos/Repo1 > > Output (shows the latest revision before I installed Scmbug, none of the > failed commits after installing Scmbug show up): > ----------- > jaydeep > 2009-02-18 00:12:41 -0800 (Wed, 18 Feb 2009) > 7 > message > > Apparently, the "-t" option is what causes the problem. I found that the > value of $svn_txn is derived from %TXN% in the file pre-commit.bat. So my > question is, what is %TXN%? Where does this value come from? It looks like > an environment variable (like we have %PATH% in Windows), but I'm not able > to find it anywhere, or track its value . The same thing applies to %REPOS% > too. Please let me know what these mean. > > I would also like to know, does Subversion store past transaction IDs > anywhere? If so, where? I checked under "C:\Repos\Repo1\db\transactions" and > did not find anything relevant. I would like to run the above svnlook > command using the "-t" option and a valid TXN value. > > I hope the information above helps in debugging the issue. Let me know if > there is anything else you need. > > Regards, > Jaydeep. > > > On Tue, Feb 24, 2009 at 10:03 PM, Kristis Makris > <[email protected]>wrote: > >> On Tue, 2009-02-24 at 12:03 +0530, Jaydeep Ghurye wrote: >> >> > Apparently, the log file is not providing any additional information >> > than what we already have. Kindly let me know if there is anything >> > else that we can do to get to the root of this problem. >> >> Can you also raise the debugging to DEBUG (instead of just WARN). There >> should be a lot more debugging information before this message. >> >> > Can you tell me if there is any tool available that can help me debug >> > SCMBUG at run-time? I mean an editor with debugging facilities, like >> > you have in Turbo C++ or Visual Basic, where you have features for >> > adding breakpoints, adding a 'Watch' to variables and monitoring the >> > flow of the program using step mode etc. >> >> I don't know of such tools. But the calls to Scmbug originate from >> <repository>/hooks/{pre,post}-commit. That's where you could intercept >> them. Beware that Subversion cleans up any environment variables before >> calling these. >> >> >> >
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
