-
Notifications
You must be signed in to change notification settings - Fork 25k
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] MLModelDeploymentsUpgradeIT testTrainedModelDeployment failing #87959
Comments
Pinging @elastic/ml-core (Team:ML) |
To debug the failure in elastic#87959.
To debug the failure in #87959.
Unfortunately this ^^ failure did not have the enabled logging yet so we've got to wait for another failure. |
I had another failure today: https://gradle-enterprise.elastic.co/s/rhoh2merwpz5o |
Here are rolling upgrade logs from a recent failure: https://gradle-enterprise.elastic.co/s/iubebkebq7vsi It has debug and trace lines for inference/action, etc. in 8. Note that the test is an upgrade from 8.2.4 -> 8.4.0 (there are multiple bwc tests ran in this suite) I am muting the tests. |
Unmuting to collect logs after adding more logging to version 8.2. Relates elastic#87959
Unmuting to collect logs after adding more logging to version 8.2. Relates #87959
Another instance of this failure (https://gradle-enterprise.elastic.co/s/b3ndm5tccf23w) |
Another failure here https://gradle-enterprise.elastic.co/s/lfba2yqci5eww It failed 42 times in the past 7 days. |
When the internal objects were renamed, an inappropriate bwc version restriction was put in place. This commit fixes this by allowing trained model assignment metadata updates to be serialized to nodes > 8.0.0. This is OK as the object serialization handles its BWC conditions when serializing over the wire. This closes: #87959
When the internal objects were renamed, an inappropriate bwc version restriction was put in place. This commit fixes this by allowing trained model assignment metadata updates to be serialized to nodes > 8.0.0. This is OK as the object serialization handles its BWC conditions when serializing over the wire. This closes: elastic#87959
When the internal objects were renamed, an inappropriate bwc version restriction was put in place. This commit fixes this by allowing trained model assignment metadata updates to be serialized to nodes > 8.0.0. This is OK as the object serialization handles its BWC conditions when serializing over the wire. This closes: #87959
The test has failed in the last 3 days. Possibly a backport is needed? https://gradle-enterprise.elastic.co/s/xiemsmv6cxbz6 |
The fix is now present on all active branches. |
Build scan:
https://gradle-enterprise.elastic.co/s/rrbldaxcklpvk/tests/:x-pack:qa:rolling-upgrade:v8.2.4%23twoThirdsUpgradedTest/org.elasticsearch.upgrades.MLModelDeploymentsUpgradeIT/testTrainedModelDeployment
Reproduction line:
./gradlew ':x-pack:qa:rolling-upgrade:v8.2.4#twoThirdsUpgradedTest' -Dtests.class="org.elasticsearch.upgrades.MLModelDeploymentsUpgradeIT" -Dtests.method="testTrainedModelDeployment" -Dtests.seed=B48E616E1A60493F -Dtests.bwc=true -Dtests.locale=no-NO -Dtests.timezone=America/Kralendijk -Druntime.java=17
Applicable branches:
master
Reproduces locally?:
Didn't try
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.upgrades.MLModelDeploymentsUpgradeIT&tests.test=testTrainedModelDeployment
Failure excerpt:
The text was updated successfully, but these errors were encountered: