-
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] ClassificationIT.testTooLowConfiguredMemoryStillStarts & RunDataFrameAnalyticsIT.testModelMemoryLimitLowerThanEstimatedMemoryUsage #61561
Labels
Comments
Pinging @elastic/ml-core (:ml) |
@benwtrent this looks to have failed again, this time in 7.x: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+matrix-java-periodic-fips/ES_RUNTIME_JAVA=openjdk15,nodes=general-purpose/196/ |
Yeah, more discussion here #61704 I think we have found the cause. Hopefully it will get fixed soon. It can be muted for the time being. |
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
Build scan:
https://gradle-enterprise.elastic.co/s/lqjgfg43cew4q
Note it has two failed tests
Repro line:
Reproduces locally?:
No
Applicable branches:
master
Failure history:
The method
testModelMemoryLimitLowerThanEstimatedMemoryUsage
failed for the very first faliure in last 30 days according to build-stats. I was gonna let it pass, but then I noticed thattestTooLowConfiguredMemoryStillStarts
is a new method added in today's changes. Both methods are touched in the change set. So there might be something going on.Failure excerpt:
The text was updated successfully, but these errors were encountered: