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

Is there a way to know that the submission failed due to Timeout #679

Open
gouseferoz opened this issue Jul 26, 2024 · 3 comments
Open

Is there a way to know that the submission failed due to Timeout #679

gouseferoz opened this issue Jul 26, 2024 · 3 comments

Comments

@gouseferoz
Copy link

I was wondering if there is a way to know that the execution has stopped due to the timeout? I am not sure if it already exists and it would be helpful if we have one.

@livinNector
Copy link

The signal field of the response will be SIGKILL if the execution is terminated due to a timeout, otherwise it is null.

@smark-1
Copy link

smark-1 commented Sep 13, 2024

In the latest version it doesn't appear to be documented but I found that when the run.status = "TO" the execution has been terminated because of timeout and if it is "XX" it is because of exceeding the output limit.

@Brikaa
Copy link
Member

Brikaa commented Sep 13, 2024

According to the documentation of the latest version, XX is used for reporting internal errors so it should not be relied on for determining if the output limits were exceeded. I have made a PR that sets an appropriate status for exceeding the output limits, and also reports SIGKILL when the time-limit or the output limit is exceeded to maintain backward compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants