-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] TimeSeriesLifecycleActionsIT.testHistoryIsWrittenWithFailure failing to assert step #52853
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>test-failure
Triaged test failures from CI
Comments
mark-vieira
added
>test-failure
Triaged test failures from CI
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
labels
Feb 26, 2020
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
probakowski
added a commit
to probakowski/elasticsearch
that referenced
this issue
Mar 2, 2020
This change modifies ILMHistoryStore to always apply correct settings and mappings, even if template is deleted and not yet recreated. This ensures that ILM history index is correctly managed by ILM and also fixes flaky history tests that were prone to triggenring this race. This commit also refactors and simplifies ILM history tests. Closes elastic#50353 and elastic#52853
probakowski
added a commit
that referenced
this issue
Mar 4, 2020
* Avoid race condition in ILMHistorySotre This change modifies ILMHistoryStore to always apply correct settings and mappings, even if template is deleted and not yet recreated. This ensures that ILM history index is correctly managed by ILM and also fixes flaky history tests that were prone to triggenring this race. This commit also refactors and simplifies ILM history tests. Closes #50353 and #52853 * Review comment Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
probakowski
added a commit
to probakowski/elasticsearch
that referenced
this issue
Mar 4, 2020
* Avoid race condition in ILMHistorySotre This change modifies ILMHistoryStore to always apply correct settings and mappings, even if template is deleted and not yet recreated. This ensures that ILM history index is correctly managed by ILM and also fixes flaky history tests that were prone to triggenring this race. This commit also refactors and simplifies ILM history tests. Closes elastic#50353 and elastic#52853 * Review comment Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
We've had a couple more failures of this specific test in the last couple of days: https://gradle-enterprise.elastic.co/s/qhraswyh3qk6g |
probakowski
added a commit
that referenced
this issue
Mar 9, 2020
* Avoid race condition in ILMHistorySotre (#53039) * Avoid race condition in ILMHistorySotre This change modifies ILMHistoryStore to always apply correct settings and mappings, even if template is deleted and not yet recreated. This ensures that ILM history index is correctly managed by ILM and also fixes flaky history tests that were prone to triggenring this race. This commit also refactors and simplifies ILM history tests. Closes #50353 and #52853 * Review comment Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> * fixed tests * backport #53306 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>test-failure
Triaged test failures from CI
There's an existing issue for this same test (#50353) but that is failing on a different assertion so it's not clear if this is the same problem. If these both have the same root cause feel free to close this as a duplicate.
https://gradle-enterprise.elastic.co/s/xmnuuygmxv4ky/tests/ao2nxxbijves6-iqisezgxfz7vq
https://gradle-enterprise.elastic.co/s/6lb3nya5vvutu/tests/ao2nxxbijves6-iqisezgxfz7vq
https://gradle-enterprise.elastic.co/s/rhh26e3fddsvq/tests/ao2nxxbijves6-iqisezgxfz7vq
https://gradle-enterprise.elastic.co/s/n5fq6qztklpb4/tests/ao2nxxbijves6-iqisezgxfz7vq
The text was updated successfully, but these errors were encountered: