Skip to content

[CI] MlDistributedFailureIT.testCloseUnassignedFailedJobAndStopUnassignedStoppingDatafeed failed #52451

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

Closed
henningandersen opened this issue Feb 18, 2020 · 1 comment · Fixed by #52461
Assignees
Labels
:ml Machine learning >test-failure Triaged test failures from CI

Comments

@henningandersen
Copy link
Contributor

Test failure against master:


org.elasticsearch.xpack.ml.integration.MlDistributedFailureIT > testCloseUnassignedFailedJobAndStopUnassignedStoppingDatafeed FAILED |  
-- | --
  | java.lang.AssertionError: expected:<failed> but was:<opened> |  
  | at org.junit.Assert.fail(Assert.java:88) |  
  | at org.junit.Assert.failNotEquals(Assert.java:834) |  
  | at org.junit.Assert.assertEquals(Assert.java:118) |  
  | at org.junit.Assert.assertEquals(Assert.java:144) |  
  | at org.elasticsearch.xpack.ml.integration.MlDistributedFailureIT.testCloseUnassignedFailedJobAndStopUnassignedStoppingDatafeed(MlDistributedFailureIT.java:237)

Did not reproduce locally using:

./gradlew ':x-pack:plugin:ml:internalClusterTest' --tests "org.elasticsearch.xpack.ml.integration.MlDistributedFailureIT.testCloseUnassignedFailedJobAndStopUnassignedStoppingDatafeed"   -Dtests.seed=115A888A8C73A817   -Dtests.security.manager=true   -Dtests.locale=mk-MK   -Dtests.timezone=Atlantic/Bermuda   -Dcompiler.java=13
@henningandersen henningandersen added >test-failure Triaged test failures from CI :ml Machine learning labels Feb 18, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@droberts195 droberts195 self-assigned this Feb 18, 2020
droberts195 added a commit to droberts195/elasticsearch that referenced this issue Feb 18, 2020
When changing a job state using a mechanism that doesn't
wait for the desired state to be reached within the production
code the test code needs to loop until the cluster state has
been updated.

Closes elastic#52451
droberts195 added a commit that referenced this issue Feb 18, 2020
When changing a job state using a mechanism that doesn't
wait for the desired state to be reached within the production
code the test code needs to loop until the cluster state has
been updated.

Closes #52451
droberts195 added a commit that referenced this issue Feb 18, 2020
When changing a job state using a mechanism that doesn't
wait for the desired state to be reached within the production
code the test code needs to loop until the cluster state has
been updated.

Closes #52451
droberts195 added a commit that referenced this issue Feb 18, 2020
When changing a job state using a mechanism that doesn't
wait for the desired state to be reached within the production
code the test code needs to loop until the cluster state has
been updated.

Closes #52451
sbourke pushed a commit to sbourke/elasticsearch that referenced this issue Feb 19, 2020
When changing a job state using a mechanism that doesn't
wait for the desired state to be reached within the production
code the test code needs to loop until the cluster state has
been updated.

Closes elastic#52451
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:ml Machine learning >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants