Re: [HTCondor-users] Job Materialisation Time

[Jeff Templon <templon@xxxxxxxxx>]

Thanks Todd,

This will work!

JT


> On 10 Dec 2024, at 21:01, Todd L Miller via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:
> 
>> Related to the discussion yesterday about delaying certain jobs, we have something that works well, with one caveat - it relies on the `QDate`, which I would have thought would have been the moment that the job appeared in the queue.
> 
> 	It's actually the moment the _cluster ad_ appeared in the queue. (Hopefully a non late-materialization submit never takes long enough for the difference to become clear.)
> 
> 	You can add the following to the job submit file in order to learn when the job was materialized.  The idea is that late materialization must
> evaluate some substitutions at job ad creation time, rather than submit time.
> 
> NOW=time()
> MY.MaterializationDate=$INT(NOW)
> 
> 	You could use a submit transform to make sure every job in your AP gets a MaterializationDate.
> 
> -- ToddM
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> 
> The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/