-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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] EarlyDeprecationIndexingIT testEarlyDeprecationIsIndexedAfterTemplateIsLoaded failing #104716
Labels
:Core/Infra/Logging
Log management and logging utilities
low-risk
An open issue or test failure that is a low risk to future releases
Team:Core/Infra
Meta label for core/infra team
>test-failure
Triaged test failures from CI
Comments
kingherc
added
:Core/Infra/Logging
Log management and logging utilities
>test-failure
Triaged test failures from CI
Team:Core/Infra
Meta label for core/infra team
labels
Jan 24, 2024
Pinging @elastic/es-core-infra (Team:Core/Infra) |
thecoop
added
low-risk
An open issue or test failure that is a low risk to future releases
and removed
blocker
labels
Jan 25, 2024
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Feb 21, 2024
this test intends to test the bulkProcessor2's request consumer before the templates are initialised. This requires the flush to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates elastic#104716
pgomulka
added a commit
that referenced
this issue
Feb 21, 2024
this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates #104716
I tweaked the test a little (to make sure that it always covers the early deprecation indexing) and enabled trace logging in #105696 |
@pgomulka here's a fresh failure for this one https://gradle-enterprise.elastic.co/s/qca37bsec4djs |
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Apr 16, 2024
this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates elastic#104716
pgomulka
added a commit
that referenced
this issue
Apr 16, 2024
…107540 this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates #104716
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Core/Infra/Logging
Log management and logging utilities
low-risk
An open issue or test failure that is a low risk to future releases
Team:Core/Infra
Meta label for core/infra team
>test-failure
Triaged test failures from CI
Build scan:
https://gradle-enterprise.elastic.co/s/batvq7lqlwwiu/tests/:x-pack:plugin:deprecation:qa:early-deprecation-rest:javaRestTest/org.elasticsearch.xpack.deprecation.EarlyDeprecationIndexingIT/testEarlyDeprecationIsIndexedAfterTemplateIsLoaded
Reproduction line:
Applicable branches:
8.12
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.xpack.deprecation.EarlyDeprecationIndexingIT#testEarlyDeprecationIsIndexedAfterTemplateIsLoaded
Failure excerpt:
The text was updated successfully, but these errors were encountered: