RE: [p4] checking success / failure of sync

A writable file won't be replaced by perforce, and IMO causes a sync
operation to fail.  That's pretty common around here.

But, back to the original question.  You might be able to discard stdout
and look for any lines being sent to stderr as an indicator that the
sync failed.

j

-----Original Message-----
From: perforce-user-admin@xxxxxxxxxxxx
[mailto:perforce-user-admin@xxxxxxxxxxxx] On Behalf Of Matthew
Janulewicz
Sent: Tuesday, December 14, 2004 4:51 PM
To: NIGGEMYER Brant; perforce-user@xxxxxxxxxxxx
Subject: Re: [p4] checking success / failure of sync


Partly opinion, partly philosophy, partly zen:

I work on the assumption that a sync NEVER fails, and maybe that's why  
there is no errorlevel set on this command. Client views not being  
properly handled are a problem with the views, not the sync action
itself.  
Short of the server crashing mid-sync (which is still not the sync  
action's fault) a sync can only 'fail' because something else is set up

incorrectly. A sync will always do exactly what you ask it to do (by way

of your client spec), success or failure depending on the quality of
your  
client spec.

I feel the same way about compilers, for what it's worth. I don't
believe  
that a compile ever 'fails' as such. An error is an error in your code,

not the compiler. So checking for a failed compile is to check the
quality  
of your code. Garbage in, garbage out. A failed compile, to me, points
to  
a level of *success* for the compiler itself. Failure = success. Chew on

that for a bit.

In that vein, this might be a sticky problem. You will have to parse  
output, but approaching it from this other angle, it would behoove you
to  
pre-verify that the client specs you are using are legit. You would have

to parse/account for all kinds of errors, probably starting with all the

permutations of '... not in client view ...', etc. I don't think there
is  
an easy way to do it.


-Matt

_______________________________________________
perforce-user mailing list  -  perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user