Condor doesn't like it when our job names contain =. When they do, it mysteriously fails to run those jobs. Unfortunately when this happens there's no clear error message or anything for a wrapper user to indicate why the jobs failed to run. This has bitten both myself and @lichtefeld at different times, so it seems worth catching.
This is an easy constraint to validate at workflow build time, so I say we do that. The main purpose of Locator s is as job names, so we can add a validator to Locator that simply makes sure there are no equals signs in the name.
Condor doesn't like it when our job names contain
=. When they do, it mysteriously fails to run those jobs. Unfortunately when this happens there's no clear error message or anything for a wrapper user to indicate why the jobs failed to run. This has bitten both myself and @lichtefeld at different times, so it seems worth catching.This is an easy constraint to validate at workflow build time, so I say we do that. The main purpose of
Locators is as job names, so we can add a validator toLocatorthat simply makes sure there are no equals signs in the name.