Add integration test coverage for actions cleanup with non-existing index #882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
scunningham
approved these changes
Nov 17, 2021
mergify bot
added a commit
that referenced
this pull request
Nov 17, 2021
…ndex (#882) (#889) (cherry picked from commit 3f02142) Co-authored-by: Aleksandr Maus <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
Adds integration test coverage for the case where the index is not found.
This is related to the defect that was not covered by the integration test:
#876
How does this PR solve the problem?
Add integration test coverage for actions cleanup with non-existing index
How to test this PR locally
or if the instance of Elasticsearch is already running:
Checklist
Related issues