Skip to content

Conversation

@davidkyle
Copy link
Member

@davidkyle davidkyle commented May 22, 2019

#42344 looks like catastrophic failures but the root cause was #42347.

The reason the pending tasks were not terminated is in the clean up code which would iterate over each data frame, stop it and assert that its state == stopped. #42347 meant that the state was reported incorrectly. If there was more than one data frame created in the test then others would not be stopped due to the assertion being thrown inside the for loop.

I've changed the logic to stop all data frames before assert that they are in state stopped and re-enabled the tests as the root cause was fixed in #42347.

Closes #42344

@davidkyle davidkyle added >test Issues or PRs that are addressing/adding tests v8.0.0 v7.2.0 :ml/Transform Transform labels May 22, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

@davidkyle
Copy link
Member Author

retest this please

@davidkyle davidkyle merged commit 306faa4 into elastic:master May 24, 2019
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
Reverts muting of tests and simplifies the test teardown
so that all data frames will be stopped 

This reverts commit 4a94387
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:ml/Transform Transform >test Issues or PRs that are addressing/adding tests v7.2.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] Data Frame IT failures due to task not terminating

4 participants