Story #3696

[Workbench] Improve log viewer to more effectively expose relevant information for failed jobs

Added by Abram Connelly over 3 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
08/26/2014
Due date:
% Done:

0%

Estimated time:
Story points:
2.0

Description

When reviewing why a job has failed I find myself wading through a lot of text to get at the single line of relevance. When multiple tasks are running, they all give an error message when they are killed because of the root task that caused the failure. This is one of the confusing issues when trying to debug what happened in a failed job. For example, if I have a job running 8 tasks concurrently and one of the tasks failed, the other 7 will be killed, emitting error messages. To someone not used to seeing tasks killed in this manner, it could be confusing as to why the other 7 tasks failed.

It would be nice to have a report of the failed job with a clear, concise message of why the job failed, perhaps displaying the root task that caused the failure along with information that might be relevant to debugging the issue.

History

#1 Updated by Tom Clegg over 3 years ago

  • Subject changed from Show relevant information for failed jobs to [Workbench] Improve log viewer to more effectively expose relevant information for failed jobs
  • Story points set to 2.0

#2 Updated by Tom Clegg over 3 years ago

  • Target version set to Arvados Future Sprints

#3 Updated by Tom Clegg 9 months ago

  • Status changed from New to Closed

#4 Updated by Tom Clegg 9 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF