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.

Sign up for GitHub

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

Jump to bottom

[7.7] Mark rule run as failure if there was an error (#62383) #62514

Merged
merged 1 commit into from
Apr 3, 2020
Merged

[7.7] Mark rule run as failure if there was an error (#62383) #62514

merged 1 commit into from
Apr 3, 2020

Conversation

rylnd
Copy link
Contributor

@rylnd rylnd commented Apr 3, 2020

Backports the following commits to 7.7:

@rylnd
Mark rule run as failure if there was an error (elastic#62383)
cb5c510 
While we still let the rule execute in the case of gap errors and
stopped ML jobs, we now mark that execution as a failure instead of a
success.
@rylnd rylnd added the backport label Apr 3, 2020
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@rylnd rylnd merged commit d3d8ea8 into elastic:7.7 Apr 3, 2020
@rylnd rylnd deleted the backport/7.7/pr-62383 branch April 3, 2020 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
backport
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rylnd @kibanamachine