Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Misspelled requirement
- Date: Thu, 3 Feb 2022 12:41:20 -0600
- From: Jacek Kominek <jkominek@xxxxxxxx>
- Subject: Re: [HTCondor-users] Misspelled requirement
Hi Todd,
It's quite possible the typo was reported (we are running HTCondor
8.9.11), I only got a report about a forever-idle job without further
specifics, so it is likely that the user didn't catch or understand it.
Thank you for the response, it clarifies it a bit. What bothers me the
most is that it did get processed as a valid condor job requirement (not
a variable/macro) even though the resource was non-existent in the
system. This is a very particular and limited namespace, from what I
know, since you can only request CPUs, GPUs, memory or diskspace.
Correct me if I am wrong, but should anything else be flat out rejected
in such context?
-Jacek
On 2/3/22 11:56, Todd Tannenbaum wrote:
On 2/3/2022 11:48 AM, Jacek Kominek via HTCondor-users wrote:
Hi all,
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?
Hi Jacek,
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 above:
$ cat test.sub
requestCUPS = 8
executable = /bin/true
queue
$ condor_submit test.sub
Submitting job(s).
1 job(s) submitted to cluster 2.
WARNING: the line 'requestCUPS = 8' was unused by condor_submit. Is it
a typo?
--
Jacek Kominek, PhD
University of Wisconsin-Madison
1552 University Avenue, Wisconsin Energy Institute 4154 Madison, WI
53726-4084, USA
jkominek@xxxxxxxx