[Crunch] [UX] Job log should warn user more clearly when no output is recorded
Comparing job: qr1hi-8i9sb-maixhdz21fh9z0n to job: qr1hi-8i9sb-h0z9l6pwcwyhy9h
Comparing scripts: https://workbench.qr1hi.arvadosapi.com/repositories/qr1hi-s0uqq-nft5jq6b5kpvo9t/blob/28e05a2d1d398bf3cb39198f29f513b8dbbfde73/crunch_scripts/varscan.py to https://workbench.qr1hi.arvadosapi.com/repositories/qr1hi-s0uqq-nft5jq6b5kpvo9t/blob/f1648526332bd9c09c6915a5cd16edf065ad5dea/crunch_scripts/varscan.py (to their respective jobs)
the only difference in job in the first job is that I forgot to write data to keep. The log for not writing data to keep was
child 4218 on compute4.1 exit 0 success=false
There needs to be some indication saying that you need to write to keep in order to succeed. This log error is way too vague.
7313: crunch-job reports an error when a task doesn't record state.