-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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: org.elasticsearch.client.MachineLearningIT » testStopDataFrameAnalyticsConfig #43924
Labels
Comments
alpar-t
added
>test-failure
Triaged test failures from CI
:ml
Machine learning
v8.0.0
v7.4.0
labels
Jul 3, 2019
Pinging @elastic/ml-core |
Ah, this is so simple actually. We call start and assert that the state is |
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 4, 2019
In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes elastic#43924
pull bot
pushed a commit
to Mattlk13/elasticsearch
that referenced
this issue
Jul 4, 2019
In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes elastic#43924
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 4, 2019
In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes elastic#43924
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 4, 2019
…c#43957) In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes elastic#43924
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 4, 2019
#43968) In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes #43924
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 4, 2019
…3967) In MachineLearningIT.testStopDataFrameAnalytics we call start and then assert the state is `started`. However, if things go fast enough, the state could have already changed to `reindexing` or `analyzing`. The test has been failing occasionally due to the state being `reindexing`. We fix this by simply asserting the state is either of `started`, `reindexing` or `analyzing`. Closes #43924
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Example build failure
https://scans.gradle.com/s/dkjie5h3phbx4/tests/43nmsh6ur4gh6-yfbilbda7ksos
https://scans.gradle.com/s/dkjie5h3phbx4/tests/43nmsh6ur4gh6-yfbilbda7ksos
Reproduction line
does not reproduce locally, seems to reproduce when the build is running with
--parallel
Example relevant log:
Frequency
7 times in the past 6 days
The text was updated successfully, but these errors were encountered: