Bug #7313
closed
[Crunch] [UX] Job log should warn user more clearly when no output is recorded
Description
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.
Updated by Brett Smith over 9 years ago
- Subject changed from [SDK] [UX] Not uploading any data to keep shows vague log to [Crunch] [UX] Job log should warn user more clearly when no output is recorded
- Category set to Crunch
- Target version set to Arvados Future Sprints
Updated by Tom Clegg about 9 years ago
Just before or after logging this line
child 4218 on compute4.1 exit 0 success=false
crunch-job should also say
ERROR: Task process exited 0, but never updated its task record to indicate success and record its output.
Updated by Brett Smith about 9 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:714c555bda26a6a27fad7caef382d1d6705ad215.
Updated by Brett Smith about 9 years ago
- Target version changed from Arvados Future Sprints to 2015-12-02 sprint