Project

General

Profile

Bug #24412

mark_failed_submissions() should only update to Completed if job is completed

Added by Marc Mengel 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Start date:
05/13/2020
Due date:
% Done:

0%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

There are basically two cases:
1) really short jobs -- the job is New, but it completes before we even see it
2) Landscape is down/slow

In those cases, we have jobs sitting around as New for a long time.

We don't want to mark them LaunchFailed if they have logs; but if we mark
them Running,for example, and Landscape is down; we won't check them anymore,
and they'll never get marked Completed.

We also need to double check why the job check isn't working -- possilby we fail
getting the logs also if Landscape is unhappy.

Associated revisions

Revision 3b82f73a (diff)
Added by Marc Mengel 7 months ago

change for issue #24412

Revision 6fae21ee (diff)
Added by Marc Mengel 7 months ago

more tidbits for #24412

History

#1 Updated by Marc Mengel 7 months ago

Okay, so this is more broken than I thought.

It's not getting status for the job because it's not including the .0
in the path when it looks.

So we don't get any info because we aren't actually getting the job status
from the joblogs like we thought... Sigh.

Also available in: Atom PDF