Bug #4748

[API] Explain why there are 21 jobs with log = ""

Added by Radhika Chippada over 3 years ago. Updated about 1 year ago.

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

0%

Estimated time:
Story points:
-

Description

Topaz noticed during reviewing #4477 update that there 21 jobs with empty logs. It would be good to understand why they are empty.

From IRC conversation:

14:23 topaz: 2.1.0 :022 > Job.where(log: "").count
14:23 topaz: (5.0ms) SELECT COUNT FROM "jobs" WHERE "jobs"."log" = ''
14:23 topaz: => 21


Related issues

Related to Arvados - Bug #7123: [Crunch] Should not save any log record when log writing failsResolved2015-11-09

History

#1 Updated by Radhika Chippada over 3 years ago

  • Description updated (diff)

#2 Updated by Tom Clegg over 3 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

#3 Updated by Tom Clegg about 1 year ago

  • Subject changed from [API] Explain why there are 21 jobs with log = "" to [API] Explain why there are 21 jobs with log = ""
  • Status changed from New to Closed

#4 Updated by Tom Clegg about 1 year ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF