Hi Kristis,
I enabled debugging as instructed by you. Here is the output
from the scmbug_glue.log file:
2009/02/23 22:10:15 Scmbug WARN> Glue.pm:109:Scmbug::Glue::Glue::process -
---------------------------------------------------------
2009/02/23 22:10:18 Scmbug WARN>
SCM.pm:307:Scmbug::Glue::SCM::prepare_activity - Preparing for VERIFICATION
2009/02/23 22:10:28 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 ''.
**
**
*******************************************
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 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.
Also, can such a tool be used to monitor Scmbug when it is run by another
program? All the editors mentioned above generally run the program within
their own native environment, which allows them to track values of variables
and other information. But, in this case, the various Perl files and modules
of Scmbug are being run indirectly by another program (I don't know where
the calls originate from), and not from within the editor's environment. For
example, how can I go about doing a 'Commit' using TortoiseSVN on my client
machine and then checking the values of various variables in, say, SCM.pm on
the server while the commit is in progress?
Thanks a lot for your help.
Regards,
Jaydeep.
On Fri, Feb 20, 2009 at 10:36 PM, Kristis Makris <[email protected]>wrote:
>
> > 1) VisualSVN server with Subversion 1.5.5.
>
> So, I'm wondering if something changed between the log format reported
> by Subversion 1.5.1 and Subversion 1.5.5 that caused our log message
> parsing to fail.
>
> http://bugzilla.mkgnu.net/show_bug.cgi?id=1337
>
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
