[HTCondor-users] Bug in 25.0 python bindings

[Jeff Templon <templon@xxxxxxxxx>]

Hi,

shist=schedd.history(  since="CompletionDate < %d" % (now - 8*3600), constraint = 'JobStatus == 4', projection=['ProcId', 'ClusterId', 'JobStatus', "AccountingGroup", "AcctGroup", "Owner", "CompletionDate", 'CpusProvisioned', 'JobCurrentStartDate'], match=512)

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

  File "/usr/lib64/python3.9/site-packages/htcondor2/_schedd.py", line 446, in history

    return self._history(HistorySrc.ScheddJob, constraint, projection, match, since)

  File "/usr/lib64/python3.9/site-packages/htcondor2/_schedd.py", line 377, in _history

    raise ValueError("since string must be in the form {clusterID}.{procID}")

ValueError: since string must be in the form {clusterID}.{procID}

According to the docs, that form is ONE of the options:

since (Union[int, str, ExprTree]) â 

A cluster ID, job ID, or _expression_. If a cluster ID (passed as an integer) or job ID (passed as a string in the format{clusterID}.{procID}), only jobs recorded in the history file after (and not including) the matching ID will be returned. If an _expression_ (including strings that arenât job IDs), jobs will be returned, most-recently-recorded first, until the _expression_ becomes true; the job making the _expression_ become true will not be returned. Thus, 1038 and "clusterID == 1038" return the same set of jobs.

If None, return all (matching) jobs.

The _expression_ used evaluates to 'CompletionDate < 1771809907â .

JT