-
Notifications
You must be signed in to change notification settings - Fork 25k
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][master] DocsClientYamlTestSuiteIT put-auto-follow-pattern #53430
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
Comments
mayya-sharipova
added
>test-failure
Triaged test failures from CI
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
labels
Mar 11, 2020
Pinging @elastic/es-distributed (:Distributed/CCR) |
And a failure on 7.x
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob-unix-compatibility/os=debian-9&&immutable/630/console |
tlrx
added a commit
that referenced
this issue
Mar 24, 2020
DocsClientYamlTestSuiteIT sometimes fails for CCR related tests because tests are started before the license is fully applied and active within the cluster. The first tests to be executed then fails with the error noticed in #53430. This can be easily reproduced locally by only running CCR docs tests. This commit adds some @before logic in DocsClientYamlTestSuiteIT so that it waits for the license to be active before running CCR tests. Closes #53430
tlrx
added a commit
that referenced
this issue
Mar 24, 2020
DocsClientYamlTestSuiteIT sometimes fails for CCR related tests because tests are started before the license is fully applied and active within the cluster. The first tests to be executed then fails with the error noticed in #53430. This can be easily reproduced locally by only running CCR docs tests. This commit adds some @before logic in DocsClientYamlTestSuiteIT so that it waits for the license to be active before running CCR tests. Closes #53430
tlrx
added a commit
that referenced
this issue
Mar 24, 2020
DocsClientYamlTestSuiteIT sometimes fails for CCR related tests because tests are started before the license is fully applied and active within the cluster. The first tests to be executed then fails with the error noticed in #53430. This can be easily reproduced locally by only running CCR docs tests. This commit adds some @before logic in DocsClientYamlTestSuiteIT so that it waits for the license to be active before running CCR tests. Closes #53430
tlrx
added a commit
that referenced
this issue
Mar 24, 2020
DocsClientYamlTestSuiteIT sometimes fails for CCR related tests because tests are started before the license is fully applied and active within the cluster. The first tests to be executed then fails with the error noticed in #53430. This can be easily reproduced locally by only running CCR docs tests. This commit adds some @before logic in DocsClientYamlTestSuiteIT so that it waits for the license to be active before running CCR tests. Closes #53430
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
Log : https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=centos-8&&immutable/627/console
Build Scans: https://gradle-enterprise.elastic.co/s/t7pibrqbzjvsm
REPRODUCE WITH: ./gradlew ':docs:integTestRunner' --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/ccr/apis/auto-follow/put-auto-follow-pattern/line_15}"
-Dtests.seed=1FB43FBC4EBFC245
-Dtests.security.manager=true
-Dtests.locale=da
-Dtests.timezone=America/Cuiaba
-Dcompiler.java=13
Doesn't reproduce for me
Possibly related to : #36815
The text was updated successfully, but these errors were encountered: