[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] ExitCode persistence in held job
- Date: Thu, 12 Nov 2020 22:54:19 +0000
- From: Jaime Frey <jfrey@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] ExitCode persistence in held job
> On Nov 9, 2020, at 1:14 PM, Michael Pelletier via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:
> Hi folks,
> I'm trying to use periodic release to release a job after a time delay when the ExitCode from the process is EX_TEMPFAIL. However, it appears that at some point the ExitCode attribute no longer exists, so the periodic release never triggers.
> At what point does the job lose the ExitCode attribute?
> It looks like by setting the on_exit_hold_subcode to ExitCode, it can be preserved, and I think that gives me a workaround to accomplish the self-release, but I'm wondering what the boundaries of the ExitCode attribute are.
Odd. I donât see any code that will clear the ExitCode attribute.
I tried a quick test job with on_exit_hold=true, and the ExitCode is set when the job exits and goes on hold. And it remains when I release the job and it re-runs.