You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a job exceeds its max running time, Tapis sets the job's status to be FAILED.
However, this makes it hard to distinguish between jobs that failed due to some application error, and jobs that were running fine and exceeded their max running time.
To resolve this, can we add a new job status value (called something like EXPIRED_TIME_LIMIT), that will only be applied to jobs that are killed due to exceeding their max runtime?
The text was updated successfully, but these errors were encountered:
Discussed with submitter, probable best course of action is to add a condition code to the job record that would indicate EXPIRED_TIME_LIMIT (or something similar). This mechanism would be reusable for other conditions as the need arises.
Currently, if a job exceeds its max running time, Tapis sets the job's status to be
FAILED
.However, this makes it hard to distinguish between jobs that failed due to some application error, and jobs that were running fine and exceeded their max running time.
To resolve this, can we add a new job status value (called something like
EXPIRED_TIME_LIMIT
), that will only be applied to jobs that are killed due to exceeding their max runtime?The text was updated successfully, but these errors were encountered: