mark_failed_submissions() should only update to Completed if job is completed
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.
#1 Updated by Marc Mengel about 2 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.