Re: [HTCondor-users] Bug report: Job requirments do not consider 'TARGET.Cpus >= RequestCpus' if RequestCpus is a nested conditional expression

[Weiming Shi <swmtrc@xxxxxxxxx>]

Sorry about this wrong report. There is a bug in the user's requirement as we found out that cores is actually not defined...

On Wed, May 9, 2018 at 10:46 AM, Weiming Shi <swmtrc@xxxxxxxxx> wrote:

Hi htcondor community,

We are on condor version 8.5.8. We would like to report a case that we believe is a bug. I am not sure if it was reported before or not.

When a user specify a nested conditional _expression_ for RequestCpus, for instance,

RequestCpus = ifthenelse(Target.Cpus >= 5,ifthenelse(Target.Cpus <= 11,Target.Cpus,cores),5)

We can confirm that the constraint TARGET.Cpus >= RequestCpus will not be added automatically to the job requirement. This makes that matchmaking succeed but the actual claim of the slot fail.

The simple workaround is addingÂTARGET.Cpus >= RequestCpus manually in the job requirement.

Hope it has been or will be fixed in the latest stable release version.

Thanks