-
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
ML tests failing due to unfinished tasks #48512
Comments
Pinging @elastic/ml-core (:ml/Transform) |
This is probably not related to the This issue does highlight that we are not always cancelling the associated task if the C++ process for data frame analytics does not start successfully. |
A bunch of ML test failures (59) due to unfinished tasks: https://gradle-enterprise.elastic.co/s/sl7yrz5qkdjou The stacktraces are all pretty similar:
|
Another two:
Note both of them are "release-tests". Not sure if that is relevant. Not reproducible locally. |
The original report is nearly 2 years old and almost certainly fixed by a PR that's just not linked to this issue. The more recent failure from January was almost certainly caused by a temporary mismatch between the non-snapshot build ML C++ and Java code. (Probably one non-snapshot build failed.) |
This build failed multiple tests before eventually timing out:
https://gradle-enterprise.elastic.co/s/behidccsxog7w/console-log?task=:x-pack:plugin:ml:qa:native-multi-node-tests:integTestRunner
The text was updated successfully, but these errors were encountered: