[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Misspelled requirement
- Date: Thu, 3 Feb 2022 11:56:00 -0600
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Misspelled requirement
On 2/3/2022 11:48 AM, Jacek Kominek via
A user in our cluster submitted a job with a typo in its
requirements: requestCUPS rather than requestCPUS. Rather than
erroring out, the requirement was treated as valid and the job was
forever stuck in Idle (since we have no cups in our cluster). Is
this the expected behavior? Normally, if there are some
errors/typos with the classads or variables the scheduler is
pretty good at catching them and reporting shadow exceptions etc.
I wonder if the resource requests are treated differently?
Given that submit files can define custom macro names, it is a bit
challenging to detect typos like the above. However, upon job
submission, the user most definitely should have received a
prominent warning telling them they may have a typo in their submit
file. Did that warning not appear on your installation?
Here is what I see when I tried reproducing what you described
$ cat test.sub
requestCUPS = 8
executable = /bin/true
$ condor_submit test.sub
1 job(s) submitted to cluster 2.
WARNING: the line 'requestCUPS = 8' was unused by condor_submit.
Is it a typo?