Skip to content

Enable DeprecationHttpIT and resetFeatures in MlDeprecationIT#79071

Merged
pgomulka merged 7 commits intoelastic:masterfrom
pgomulka:enable_deprecation_test
Oct 14, 2021
Merged

Enable DeprecationHttpIT and resetFeatures in MlDeprecationIT#79071
pgomulka merged 7 commits intoelastic:masterfrom
pgomulka:enable_deprecation_test

Conversation

@pgomulka
Copy link
Copy Markdown
Contributor

closes #79038

  • Have you signed the contributor license agreement?
  • Have you followed the contributor guidelines?
  • If submitting code, have you built your formula locally prior to submission with gradle check?
  • If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.
  • If submitting code, have you checked that your submission is for an OS and architecture that we support?
  • If you are submitting this code for a class then read our policy for that.

@pgomulka pgomulka added the >test Issues or PRs that are addressing/adding tests label Oct 13, 2021
@pgomulka pgomulka self-assigned this Oct 13, 2021
@pgomulka pgomulka requested a review from droberts195 October 13, 2021 14:50
Comment on lines +92 to +94
// if data stream is still present, that means that previous test (could be different class) created a deprecation
// hence resetting again
resetDeprecationIndexAndCache();
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ideally this bit wouldn't be necessary after adding the feature reset to the ML test. Are you seeing a case where it is still needed?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I know, but I thought that if we have a new test and forget to clean up deprecation log this test would fail.
Or if for some reason the ML test failed cleanup, then this test would fail too.
I added it to a place where it is only executed after a check asserting about the deprecation index not existing failed

…asticsearch/xpack/deprecation/MlDeprecationIT.java

Co-authored-by: David Roberts <dave.roberts@elastic.co>
Copy link
Copy Markdown

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

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

LGTM

@pgomulka
Copy link
Copy Markdown
Contributor Author

@elasticmachine update branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>test Issues or PRs that are addressing/adding tests v8.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] DeprecationHttpIT.testDeprecationWarnMessagesCanBeIndexed fails on CI

5 participants