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

Set error status when unhandled exception is raised from runner #22

Merged
merged 1 commit into from
May 1, 2017

Conversation

eagletmt
Copy link
Member

Currently, when unhandled exception is raised from custom runner, the
execution status remains "pending" and there's no way to retry it after
the exception is fixed.

@cookpad/dev-infra @k0kubun please review

Currently, when unhandled exception is raised from custom runner, the
execution status remains "pending" and there's no way to retry it after
the exception is fixed.
stdout, stderr, status = run_command
begin
stdout, stderr, status = run_command
rescue Exception => e
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess you chose not StandardError but Exception to cover SignalException, for the case a job gets stuck and signal is sent to kill it. (I just wanted to know the background.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any kind of exception could be raised from the runner in theory and the job_execution status should not remain pending in any case.

@eagletmt eagletmt merged commit 0e4888b into cookpad:master May 1, 2017
@eagletmt eagletmt deleted the error-status branch May 1, 2017 00:22
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

Successfully merging this pull request may close these issues.

None yet

3 participants