-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[ML] use reset feature API for internal cluster ML tests #71836
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
Conversation
|
Pinging @elastic/ml-core (Team:ML) |
|
run elasticsearch-ci/bwc |
|
@elasticmachine update branch |
droberts195
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| // automatically recreated. | ||
| assertAcked(client().admin().indices().prepareDelete(nonAnnotationMlIndices).get()); | ||
| } | ||
| client().execute(ResetFeatureStateAction.INSTANCE, new ResetFeatureStateRequest()).actionGet(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should also delete the comment on lines 91-94, as this cleanup is now doing more than what that comment says. It will mean that in the future it will be possible to use this base class for tests that might leave jobs running when they complete.
Replaces the bespoke ML cleanup code with the feature reset API for internal cluster tests
Replaces the bespoke ML cleanup code with the feature reset API for internal cluster tests