[ML] Functional tests - explicitly delete jobs after setupModule tests #102882
Conversation
This file contains 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
pheyos
added
:ml
test_ui_functional
v8.0.0
release_note:skip
|
Pinging @elastic/ml-ui (:ml) |
pheyos
added
the
auto-backport
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 22, 2021
elastic#102882) This PR explicitly deletes the jobs created by the `setupModule` tests.
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 22, 2021
elastic#102882) This PR explicitly deletes the jobs created by the `setupModule` tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR explicitly deletes the jobs created by the
setupModuletests.Details
There were cases where the
setupModuletests timed out while waiting for a created job to finish. In some of those cases thecleanMlIndicesfailed in the suite'saftermethod, causing follow-up issues. With this PR we make sure that the jobs (and corresponding datafeeds) are force-deleted via the ES-API, so nothing is left behind after cleanup phase of the suite.