Hi
As I understand it, if I specify -currentrun
on the condor_q
command line, it gives me the information for just this run. For jobs that have not been restarted, I expect then this flag to make no difference, as the current run is the same as the entire job. But:
ââ(09:43:38)ââ> grep running gofact_extendrange_ganymede/ferm-378.txt
On Thu Nov 24 11:11:33 CET 2022 running on wn-lot-056.nikhef.nl
ââ(09:43:49)ââ> date
Thu Dec 15 09:43:57 CET 2022
ââ(09:43:57)ââ> condor_q -allusers -nobatch -pr an1.cpf 49718.328
-- Schedd: visar.nikhef.nl : <145.107.7.239:9618?... @ 12/15/22 09:44:16
JOB_ID Username CMD CPUS MEMREQ ST RUN_TIME WorkerNode
49718.328 templon ferm.condor 378 1 128.0 MB R 20+22:32:35 wn-lot-056
ââ(09:44:16)ââ> condor_q -allusers -nobatch -currentrun -pr an1.cpf 49718.328
-- Schedd: visar.nikhef.nl : <145.107.7.239:9618?... @ 12/15/22 09:44:30
JOB_ID Username CMD CPUS MEMREQ ST RUN_TIME WorkerNode
49718.328 templon ferm.condor 378 1 128.0 MB R 0+19:06:25 wn-lot-056
What gives? All of the currently-running jobs on the cluster are reporting the same RUN_TIME for -currrentrun
but none of them seem to have been restarted.
JT