Asserting a deprecation log exists at the correct level#79514
Merged
masseyke merged 1 commit intoelastic:7.xfrom Oct 19, 2021
Merged
Asserting a deprecation log exists at the correct level#79514masseyke merged 1 commit intoelastic:7.xfrom
masseyke merged 1 commit intoelastic:7.xfrom
Conversation
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
joegallo
approved these changes
Oct 19, 2021
Contributor
joegallo
left a comment
There was a problem hiding this comment.
+1 as long as Jenkins approves
Member
Author
|
@elasticmachine run elasticsearch-ci/docs |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
As #79492 of the ESTestCase assertWarnings methods now check that the log level is of the expected type. This commit
puts in the correct expected log level.
Relates #79492