Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Job status value for jobs that are terminated due to exceeding wall time #79

Closed
thecooltechguy opened this issue Feb 13, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@thecooltechguy
Copy link

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?

@richcar58 richcar58 self-assigned this Feb 13, 2024
@richcar58 richcar58 added the enhancement New feature or request label Feb 13, 2024
@richcar58
Copy link

richcar58 commented Feb 13, 2024

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.

@richcar58 richcar58 moved this from To Do to In Progress in Tapis Project Beta Board Feb 16, 2024
@richcar58 richcar58 moved this from In Progress to Develop in Tapis Project Beta Board Feb 23, 2024
@richcar58 richcar58 moved this from Develop to Staging in Tapis Project Beta Board Mar 22, 2024
@richcar58 richcar58 moved this from Staging to Done/Production in Tapis Project Beta Board May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

3 participants