Re: [Condor-users] Bug with TotalJobSuspendTime?

["Finch, Ralph" <rfinch@xxxxxxxxxxxx>]

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Zachary Miller
> Sent: Thursday, January 19, 2006 12:47 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Bug with TotalJobSuspendTime?
> 
> On Thu, Jan 19, 2006 at 11:05:22AM -0800, Finch, Ralph wrote:
> > condor -version
> > $CondorVersion: 6.7.13 Nov  7 2005 $
> > $CondorPlatform: INTEL-WINNT50 $
> 
> okay.
> 
> 
> > So then I tried this line:
> > 
> > && (TotalJobSuspendTime =!= UNDEFINED) && (TotalJobSuspendTime <=
> > $(MaxSuspendTime))
> 
> i think you just need to put another set of parenthesis 
> around the test and use
> of the UNDEFINED value, like this:
> 
> ((TotalJobSuspendTime =!= UNDEFINED) && (TotalJobSuspendTime 
> <= $(MaxSuspendTime)))
> 		
> condor doesn't short-circuit the boolean evaluation, so it 
> was still evaluating
> the undefined attribute and getting ERROR.  the reason it 
> works with the extra
> parenthesis then is that:
>   (FALSE && ERROR) == FALSE
> 
> i.e. the ERROR is squashed.
> 
> 
> also, this actually changed in 6.7.14, and condor does 
> short-circuit boolean
> evaluation.

OK.  But why did just

(TotalJobSuspendTime <= $(MaxSuspendTime))

work before (6.7.12 I believe) and not now?

Puzzled,

Ralph Finch, P.E.
Dept. of Water Resources
Bay-Delta Office, Room 215-13
Sacramento, CA  95814
916-653-7552
rfinch@xxxxxxxxxxxx