Project

General

Profile

Actions

Bug #20531

closed

When getting logs from child job to print error, distinguish between job couldn't start and non-zero exit

Added by Peter Amstutz 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
CWL
Target version:
Story points:
0.5
Release relationship:
Auto

Description

  • When the job failed with a non-zero exit code, just print stdout/stderr, no crunch-run
  • When the job failed to start, only print crunch-run (we won't have stdout/stderr anyway)
  • When the job failed from a signal (exit code > 127), print both

Subtasks 1 (0 open1 closed)

Task #20563: Review 20531-cwl-log-tailResolvedBrett Smith05/30/2023Actions

Related issues

Related to Arvados - Idea #20521: Python tools emit logs from googleapiclientNewActions
Actions

Also available in: Atom PDF