-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] ML ClassificationIT.testTooLowConfiguredMemoryStillStarts failure #61704
Labels
Comments
henningandersen
added
>test-failure
Triaged test failures from CI
:ml
Machine learning
v8.0.0
v7.10.0
labels
Aug 31, 2020
Pinging @elastic/ml-core (:ml) |
henningandersen
added a commit
to henningandersen/elasticsearch
that referenced
this issue
Aug 31, 2020
henningandersen
added a commit
that referenced
this issue
Aug 31, 2020
henningandersen
added a commit
that referenced
this issue
Aug 31, 2020
Muted in master and 7.x in #61705 |
Two issues:
The race condition is here: Basically, the onCrash callback is being called, but then we are raising that the on start failed. Logs:
|
@dimitris-athanasiou ^^ ping on the race |
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Sep 2, 2020
While starting the data frame analytics process it is possible to get an exception before the process crash handler is in place. In addition, right after starting the process, we check the process is alive to ensure we capture a failed process. However, those exceptions are unhandled. This commit catches any exception thrown while starting the process and sets the task to failed with the root cause error message. I have also taken the chance to remove some unused parameters in `NativeAnalyticsProcessFactory`. Relates elastic#61704
dimitris-athanasiou
added a commit
that referenced
this issue
Sep 2, 2020
While starting the data frame analytics process it is possible to get an exception before the process crash handler is in place. In addition, right after starting the process, we check the process is alive to ensure we capture a failed process. However, those exceptions are unhandled. This commit catches any exception thrown while starting the process and sets the task to failed with the root cause error message. I have also taken the chance to remove some unused parameters in `NativeAnalyticsProcessFactory`. Relates #61704
dimitris-athanasiou
added a commit
that referenced
this issue
Sep 2, 2020
…61838) (#61847) While starting the data frame analytics process it is possible to get an exception before the process crash handler is in place. In addition, right after starting the process, we check the process is alive to ensure we capture a failed process. However, those exceptions are unhandled. This commit catches any exception thrown while starting the process and sets the task to failed with the root cause error message. I have also taken the chance to remove some unused parameters in `NativeAnalyticsProcessFactory`. Relates #61704 Backport of #61838
benwtrent
added a commit
that referenced
this issue
Sep 2, 2020
Native PR addresses this test failure: elastic/ml-cpp#1465 closes #61704 closes #61561
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Sep 2, 2020
Native PR addresses this test failure: elastic/ml-cpp#1465 closes elastic#61704 closes elastic#61561
benwtrent
added a commit
that referenced
this issue
Sep 2, 2020
) * [ML] unmute testTooLowConfiguredMemoryStillStarts (#61846) Native PR addresses this test failure: elastic/ml-cpp#1465 closes #61704 closes #61561
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Build scan:
https://gradle-enterprise.elastic.co/s/xxiunoj23mvfy
Repro line:
Reproduces locally?:
It did reproduce something though a different assertion failure:
Build-stats does indicate a number of different failure.
Applicable branches:
master and 7.x
Failure history:
https://build-stats.elastic.co/goto/8942e4faac3b7916cf4ca2e0433f82cf
Looks like failures started August 27th, with around 7 failures per day.
This test was also previously reported failing in: #61561
Failure excerpt:
The text was updated successfully, but these errors were encountered: