Fw: [p4perl] sync problems

Roger Day roger.day at globalgraphics.com
Fri Mar 11 11:44:44 PST 2005


with debug set, both running

$self->Sync(....)
and
$self->Run("Sync"....)

give me "p4 unknown command. Try p4 help for info" in the return errors.

The command "user-sync" now appears in the log file like so:

Perforce server warning:
        2005/03/11 19:43:03 pid 2392 rday at mauberley 127.0.0.1 'user-client 
-o mauberley'
Perforce server warning:
        2005/03/11 19:43:04 pid 2392 rday at mauberley 127.0.0.1 'user-client 
-i'
Perforce server warning:
        2005/03/11 19:43:04 pid 2392 rday at mauberley 127.0.0.1 'user-sync 
-f //depot/swig_tests/simple_build/product.xml#head'
Perforce server warning:
        2005/03/11 19:43:04 pid 1144 rday at mauberley 127.0.0.1 'user-client 
-o mauberley'
Perforce server warning:
        2005/03/11 19:43:05 pid 892 rday at mauberley 127.0.0.1 'user-client 
-o mauberley'
Perforce server warning:
        2005/03/11 19:43:05 pid 892 rday at mauberley 127.0.0.1 'user-client 
-i'
Perforce server error:
        Date 2005/03/11 19:43:06:

Roger.




Tony Smith <tony at smee.org>
Sent by: p4perl-bounces at perforce.com
11/03/2005 17:10
 
        To:     p4perl at perforce.com
        cc: 
        Subject:        Re: Fw: [p4perl] sync problems


Could you enable some debugging in P4Perl:

$self->SetDebugLevel( 1 );

should do the trick. It should produce something to indicate commands are
being executed and the arguments that are being passed.

Tony

On Friday 11 March 2005 14:13, Roger Day wrote:
> in my script, $self->Errors returns an empty array.
>
> Roger
>
>
>
>
> Tony Smith <tony at smee.org>
> Sent by: p4perl-bounces at perforce.com
> 11/03/2005 13:52
>
>         To:     p4perl at perforce.com
>         cc:
>         Subject:        Re: Fw: [p4perl] sync problems
>
> On Friday 11 March 2005 11:31, Roger Day wrote:
> > As requested, more detail on the script:
>
> Thanks Roger. The script looks OK except for error checking. You should
> (in
> theory) check $self->Errors() after every command you execute. In some
> cases
> that's unnecessary, but certainly when things aren't going as expected
> it's a
> must. For example, something as simple as this:
>
> foreach my $e ( $self->Errors() )
> {
> print( "Perforce error: $e\n" );
> }
>
> will at least give you a clue as to what's happening.  Hope that helps.
>
> Tony
> _______________________________________________
> p4perl mailing list
> p4perl at perforce.com
> http://maillist.perforce.com/mailman/listinfo/p4perl
>
>
>
> !DSPAM:4231a75141011489316992!
_______________________________________________
p4perl mailing list
p4perl at perforce.com
http://maillist.perforce.com/mailman/listinfo/p4perl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/p4perl/attachments/20050311/803748b9/attachment-0001.html>


More information about the p4perl mailing list