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

failhard not being respected in batch/orch #54701

Closed
wants to merge 6 commits into from

Conversation

Oloremo
Copy link
Contributor

@Oloremo Oloremo commented Sep 20, 2019

What does this PR do?

Added proper detection of failhard during the orchestration\batch logic.

This is backport of the #54700, huge thanks to @mattp- for the original patch.

What issues does this PR fix or reference?

#54521

Previous Behavior

batch didn't stop upon encountering the error with failhard set to True

New Behavior

batch stops upon encountering the error with failhard set to True

Tests written?

Yes

Commits signed with GPG?

Yes

@Oloremo Oloremo requested a review from a team as a code owner September 20, 2019 14:42
@ghost ghost requested a review from Ch3LL September 20, 2019 14:42
failhard
pass failhard down to the executing state

.. versionadded:: 2019.2.2
Copy link
Contributor Author

Choose a reason for hiding this comment

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

not sure if I need to set versions in this PR

@Oloremo Oloremo force-pushed the failhard-batch-fix branch 2 times, most recently from 0ed0592 to 0ee6d07 Compare September 29, 2019 14:09
@Oloremo
Copy link
Contributor Author

Oloremo commented Sep 29, 2019

re-run full all

@dwoz dwoz changed the base branch from 2019.2 to 2019.2.1 September 29, 2019 21:02
@dwoz dwoz changed the base branch from 2019.2.1 to 2019.2 September 29, 2019 21:02
@Oloremo Oloremo changed the base branch from 2019.2 to 2019.2.1 September 29, 2019 21:05
@Oloremo Oloremo changed the base branch from 2019.2.1 to 2019.2 September 29, 2019 21:06
@Oloremo
Copy link
Contributor Author

Oloremo commented Sep 29, 2019

2019.2 code base seems unstable. Made PR for 2019.2.1 branch: #54806

@Oloremo
Copy link
Contributor Author

Oloremo commented Oct 1, 2019

Closed in favor of #54806

@Oloremo Oloremo closed this Oct 1, 2019
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.

1 participant