Re: [HTCondor-users] Misspelled requirement

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

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?