LSF job status unknown should probably be treated as HOLD not EXIT

[mp15]

The UNKNOWN status in LSF does not mean the job has actually died, just that the LSF daemon has lost touch with each other. A job may continue running in an unknown state for a long period of time and write output via shared disks. It may also recover and terminate with exit code 0. I would suggest treating it as QueueStatus.HOLD not QueueStatus.ERROR.

nextflow/modules/nextflow/src/main/groovy/nextflow/executor/LsfExecutor.groovy

Line 215 in 9386082

'UNKWN': QueueStatus.ERROR,