I’m working on a WDL task that runs something with very verbose logging. The job appears to run successfully — the script return code is 0 and the outputs are delocalized — but then Cromwell seems to be marking it as failed because the stderr contains the string OutOfMemoryError (I think because it logs a java command with an -XX:OnOutOfMemoryError parameter). This shows up in the metadata:
"message": "stderr for job HailMerge.HailMerge:NA:1 contained one of the `memory-retry` error-keys specified in the config. Job might have run out of memory."
Is there any per-workflow or per-task way to disable this log parsing for the memory retry feature, which I’m not using?