-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
SnapshotLifecycleRestIT#testPolicyManualExecution failed #48531
Comments
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
I've actually seen this failure before, I believe it's the same root cause as #48017. |
I've added some extra logging in #48612 that will hopefully help catch this failure. I'll try to keep an eye out for failures but if you find a failure for this test please ping me. |
@gwbrown Not sure if this is related, but some of these SLM tests just failed again ( https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob+fast+part2/2563/
Edit: Doesn't reproduce for me :( |
And another failure of this in https://gradle-enterprise.elastic.co/s/s6rpuelnp5lda
|
These policies store statistics, but since stats updating is asynchronous, it's possible for the update from one test to bleed into a separate one. This change switches the tests to use separate policy ids so that their stats are tracked independently. It also relaxes the checking constraint in one of the tests. Hopefully this: Resolves elastic#48531 Resolves elastic#48017
These policies store statistics, but since stats updating is asynchronous, it's possible for the update from one test to bleed into a separate one. This change switches the tests to use separate policy ids so that their stats are tracked independently. It also relaxes the checking constraint in one of the tests. Hopefully this: Resolves #48531 Resolves #48017
…1075) These policies store statistics, but since stats updating is asynchronous, it's possible for the update from one test to bleed into a separate one. This change switches the tests to use separate policy ids so that their stats are tracked independently. It also relaxes the checking constraint in one of the tests. Hopefully this: Resolves elastic#48531 Resolves elastic#48017
These policies store statistics, but since stats updating is asynchronous, it's possible for the update from one test to bleed into a separate one. This change switches the tests to use separate policy ids so that their stats are tracked independently. It also relaxes the checking constraint in one of the tests. Hopefully this: Resolves #48531 Resolves #48017
…1075) These policies store statistics, but since stats updating is asynchronous, it's possible for the update from one test to bleed into a separate one. This change switches the tests to use separate policy ids so that their stats are tracked independently. It also relaxes the checking constraint in one of the tests. Hopefully this: Resolves elastic#48531 Resolves elastic#48017
This build failed: https://gradle-enterprise.elastic.co/s/gxyu6m3t7am7y
The text was updated successfully, but these errors were encountered: