Skip to content

Fix parsing of the stop element in step XML #4714

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

Closed

Conversation

hpoettker
Copy link
Contributor

Resolves #1287.

Previously, users were forced to set the attribute exit-code of the stop element to "" as a work-around in some cases as the default value STOPPING or any non-null value of exit-code would lead to failing job restarts.

Previously, users were forced to set the attribute `exit-code` of the element to `""` as a work-around to prevent failing restarts.
@hpoettker hpoettker force-pushed the fix-stop-in-batch-xsd-3 branch from 4672f58 to ec661aa Compare November 24, 2024 14:54
@fmbenhassine
Copy link
Contributor

Thank you for fixing this! I remember I worked on a reproducer (as you might have seen in the original issue), but I've never got the chance to fix the issue (or more precisely, to prioritize the issue).

Rebased and merged as 39c593e. Thanks again for all your contributions! Really appreciated 👍

@hpoettker hpoettker deleted the fix-stop-in-batch-xsd-3 branch December 6, 2024 13:44
@hpoettker hpoettker restored the fix-stop-in-batch-xsd-3 branch December 6, 2024 13:44
@hpoettker hpoettker deleted the fix-stop-in-batch-xsd-3 branch December 6, 2024 13:44
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.

Job restart after stop fails
2 participants