Re: [HTCondor-users] Regular Expressions in -constraint

["O'NEAL Mark" <mark.oneal@xxxxxxxxxxx>]

Greg,

 

Yes I could imagine I don’t have the escaping correct, I found limited mention of how to handle it for the Windows CMD shell in the manual.  Thanks for pointing to the DEBUG macros.

 

I tried it with several different levels:

SCHEDD_DEBUG = D_FULLDEBUG D_COMMAND

SCHEDD_DEBUG = D_FULLDEBUG D_DAEMONCORE

SCHEDD_DEBUG = D_FULLDEBUG D_ALL

 

but never found entries for my condor_q command.  I tried searching for various portions of the requirements _expression_ string as I expected them to exist in the log, like ‘lidarMatching’, ‘constraint’, ‘regexps’.

 

Mark

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Greg Thain
Sent: Thursday, November 7, 2019 10:19 AM
To: htcondor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] Regular Expressions in -constraint

 

This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email.

 

On 11/6/19 12:00 PM, O'NEAL Mark via HTCondor-users wrote:

Greg,

 

Thanks for your detailed response.

 

 

Following Christoph’s example I also tried:

condor_q -nobatch -const “ “lidarMatching” == regexps(“”(lidarMatching)””, JobBatchName, “”\1””) “

 

and similarly didn’t return any matches.  I will do some more work with it.

 

 

I suspect the problem here is shell quoting.  One of the best ways to debug what condor actually sees in this case is to turn up the schedd's debugging level by setting something like

 

SCHEDD_DEBUG = D_FULLDEBUG D_COMMAND

 

in your condor_config file, then run condor_reconfig.  If you schedd is very busy, you may want to remove this verbosity after debugging.

 

In the SchedLog, it will print out the requirements _expression_ string as sent from the tool, after all the quoting and escaping has happened. 

 

-greg