Skip to content
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

[7.x] Add aditional logging for ILM history store tests (#5062… #50678

Merged
merged 2 commits into from Jan 6, 2020

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Jan 6, 2020

Backports the following commits to 7.x:

These tests use the same index name, making it hard to read logs when
diagnosing the failures. Additionally more information about the current
state of the index could be retrieved when failing.

This changes these two things in the hope of capturing more data about
why this fails on some CI nodes but not others.

Relates to elastic#50353

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@dakrone dakrone added backport :Data Management/ILM+SLM Index and Snapshot lifecycle management >non-issue v7.6.0 labels Jan 6, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/ILM+SLM)

@dakrone
Copy link
Member Author

dakrone commented Jan 6, 2020

@elasticmachine run elasticsearch-ci/2

2 similar comments
@dakrone
Copy link
Member Author

dakrone commented Jan 6, 2020

@elasticmachine run elasticsearch-ci/2

@dakrone
Copy link
Member Author

dakrone commented Jan 6, 2020

@elasticmachine run elasticsearch-ci/2

@dakrone dakrone changed the title [7.x] Add aditional logging for ILM history store tests (#50624) [7.x] Add aditional logging for ILM history store tests (#5062… Jan 6, 2020
@dakrone dakrone merged commit 552edd8 into elastic:7.x Jan 6, 2020
@dakrone dakrone deleted the backport/7.x/pr-50624 branch January 6, 2020 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants