Bug #4477
closed
[Workbench] Log tab not available
Added by Bryan Cosca about 10 years ago.
Updated about 10 years ago.
Assigned To:
Radhika Chippada
Description
I get a blank box with a reload tab. jobs/qr1hi-8i9sb-i4pplxizsmn0ign#Log
- Category set to Workbench
- Target version set to Bug Triage
- Subject changed from Log tab not available to [Workbench] Log tab not available
- Status changed from New to In Progress
- Assigned To set to Radhika Chippada
- Target version changed from Bug Triage to 2014-12-10 sprint
Looking at the Advanced tab for the job, I see that this job has no log. It is desirable that we handle an error case like this by showing proper message, rather than throw an error page at the user.
Do we know why jobs are getting their "log" field set to an empty string at all? Is that desired behavior?
Looping back in our conversation on IRC: this branch LGTM to solve the problem of the user being shown a confusing error message, but I'd like to add a ticket to figure out why we have 21 jobs in production that have Job.log == "" and whether there's a deeper underlying problem to solve there.
Created #4748 to answer the question why the logs are empty for some jobs.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:c3695bc7282996d66fb1922d7971aa86fb497968.
- Subject changed from [Workbench] Log tab not available to [Workbench] Log tab not available
- Story points set to 0.5
Also available in: Atom
PDF
Updated by Tim Pierce 
Updated by Radhika Chippada 
Updated by