[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] end-time for failed jobs



I see only 1 sec. gap for 24 jobs out of 154193 records in the history:

[root@serv07 ~]# condor_history -format "%d\n" 'ClusterId' | wc -l
154193
[root@serv07 ~]# condor_history -format "%d\n" 'CompletionDate - EnteredCurrentStatus' -const 'CompletionDate != 0 && CompletionDate != EnteredCurrentStatus' | sort | uniq -c
     24 1
[root@serv07 ~]# 


EnteredCurrentStatus appears to be identical to CompletionDate. The plus side is I save almost 49 sec. on average using only EnteredCurrentStatus compare to using ifThenElse _expression_ on my system.

Cheers,
Santanu

So, I think I can live with 1 second of
A little exploration...

In a history file with 18907 jobs (rotated, darn!), the largest gap was 4 seconds.

$ condor_history -format "%d\n" 'CompletionDate - EnteredCurrentStatus' -const 'CompletionDate != 0 && CompletionDate != EnteredCurrentStatus' | sort | uniq -c
    238 1
     82 2
     63 3
     37 4

Best,


matt
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/