IsValidCheckpointPlatform is automatically inserted into the Requirements for the Execute nodes to ensure that Standard universe jobs that are being resumed after a checkpoint will not match machines that they cannot resume on.
The sub _expression_ TARGET.JobUniverse isnt 1 is how this is limited to standard universe. Standard universe is a (nearly) obsolete universe that only a very small number of Condor users that are still using - in fact. Standard universe has been removed from the latest version of HTCondor.
So you can safely ignore IsValidCheckpointPlatform and assume that the reason jobs are stuck in idle is the INO_USER _expression_.
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Nagaraj Panyam <pn@xxxxxxxxxxx>
Sent: Wednesday, March 24, 2021 1:15 AM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] unwelcome job classad
All of a sudden all jobs of all users are idle and I find the reason as
below. Point is, I myself have put in the requirement for INO_USER, but
I have not put in the requirement for IsValidcheckpointPlatform. Could
it be in some updated packages? How to take it out?
The Requirements _expression_ for this slot is
INO_USER == true
(TARGET.JobUniverse isnt 1 ||
((MY.CheckpointPlatform isnt undefined) &&
((TARGET.LastCheckpointPlatform is MY.CheckpointPlatform) ||
(TARGET.NumCkpts == 0))))
This slot defines the following attributes:
CheckpointPlatform = "LINUX X86_64 3.10.0-1160.11.1.el7.x86_64
normal N/A avx avx2 ssse3 sse4_1 sse4_2"
The Requirements _expression_ for this slot reduces to these conditions:
Step Matched Condition
----- -------- ---------
 0 INO_USER == true
 0 IsValidCheckpointPlatform
Thanks a lot!
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: