Re: [HTCondor-users] RemoteWallClockTime doesn't reset when failed job reruns

[Michael Pelletier <michael.v.pelletier@xxxxxxxxxxxx>]

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of David Cohen
Sent: Tuesday, January 26, 2021 4:09 AM
Subject: [External] [HTCondor-users] RemoteWallClockTime doesn't reset when failed job reruns

Hi,
A user of ours was using a false exit code to make jobs rerun from a checkpoint noticed that RemoteWallClockTime doesn't reset when the job rerun.
Is that an intended behavior of the walltime counter?

Best regards,
David
--------------

Yes, that's an intended behavior. The RemoteWallClockTime is a cumulative stat. I use it in an expression with RemoteUserCpu and RemoteSysCpu to determine the accuracy of the job's CPU request. The expression (time() - JobCurrentStartDate) will show you the wall clock time for the current incarnation of the job.

	-Michael Pelletier.