-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[ML] [CI] DetectionRulesIT.testCondition failure #31916
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
Labels
Comments
Pinging @elastic/ml-core |
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 11, 2018
The test failure in elastic#31916 revealed that updating rules on a job was modifying the detectors list in-place. That meant the old cluster state and the updated cluster state had no difference and thus the change was not propagated to non-master nodes. This commit fixes that and also reviews all of ML metadata in order to ensure immutability. Closes elastic#31916
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 12, 2018
The test failure in #31916 revealed that updating rules on a job was modifying the detectors list in-place. That meant the old cluster state and the updated cluster state had no difference and thus the change was not propagated to non-master nodes. This commit fixes that and also reviews all of ML metadata in order to ensure immutability. Closes #31916
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Jul 12, 2018
The test failure in elastic#31916 revealed that updating rules on a job was modifying the detectors list in-place. That meant the old cluster state and the updated cluster state had no difference and thus the change was not propagated to non-master nodes. This commit fixes that and also reviews all of ML metadata in order to ensure immutability. Closes elastic#31916
dimitris-athanasiou
added a commit
that referenced
this issue
Jul 12, 2018
The test failure in #31916 revealed that updating rules on a job was modifying the detectors list in-place. That meant the old cluster state and the updated cluster state had no difference and thus the change was not propagated to non-master nodes. This commit fixes that and also reviews all of ML metadata in order to ensure immutability. Closes #31916
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This test fails with the error:
It appears the updated rules are not being picked up.
Reproduces fairly frequently for me ~ every other time:
The text was updated successfully, but these errors were encountered: