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

org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT » test {yaml=reference/ilm/start-stop-ilm/line_56} fails with expecting STOPPING but was STOPPED #46528

Closed
alpar-t opened this issue Sep 10, 2019 · 2 comments · Fixed by #46559
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >test-failure Triaged test failures from CI

Comments

@alpar-t
Copy link
Contributor

alpar-t commented Sep 10, 2019

https://gradle-enterprise.elastic.co/s/qz63x47f55v2m/tests/jbm2x6tnwtxku-ov7tbnxyfm6qe

:docs:integTestRunnerorg.elasticsearch.smoketest.DocsClientYamlTestSuiteIT » test {yaml=reference/ilm/start-stop-ilm/line_56} (0.480s)
java.lang.AssertionError: 
Failure at [reference/ilm/start-stop-ilm:78]: $body didn't match expected value:
                         $body: 
                  operation_mode: expected String [STOPPING] but was String [STOPPED]

Caused by: java.lang.AssertionError: 
$body didn't match expected value:
                         $body: 
                  operation_mode: expected String [STOPPING] but was String [STOPPED]

Reproduction line:

./gradlew ':docs:integTestRunner' --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/ilm/start-stop-ilm/line_56}" -Dtests.seed=3D5129E7020BB3D4 -Dtests.security.manager=true -Dtests.locale=zh-HK -Dtests.timezone=America/Thule -Dcompiler.java=12 -Druntime.java=11
@alpar-t alpar-t added >test-failure Triaged test failures from CI :Data Management/ILM+SLM Index and Snapshot lifecycle management labels Sep 10, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

alpar-t added a commit that referenced this issue Sep 10, 2019
@mark-vieira
Copy link
Contributor

Here's another instance of this. Doesn't look like the mute actually worked?

https://gradle-enterprise.elastic.co/s/2dj7prdperjns/tests/failed

dakrone added a commit to dakrone/elasticsearch that referenced this issue Sep 10, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves elastic#46528
dakrone added a commit that referenced this issue Sep 11, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves #46528
dakrone added a commit that referenced this issue Sep 11, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves #46528
dakrone added a commit that referenced this issue Sep 11, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves #46528
dakrone added a commit that referenced this issue Sep 11, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves #46528
dakrone added a commit that referenced this issue Sep 11, 2019
This uses whatever the server retrieves, rather than hardcoded
"STOPPING" and "STOPPED" since the server may go to STOPPED before the
request is issued.

Resolves #46528
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants