-
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
Fix accounting in ModelLoadingServiceTests #55307
Conversation
Pinging @elastic/ml-core (:ml) |
12f69e9
to
bdabc34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test failures? org.elasticsearch.xpack.ml.inference.loadingservice.ModelLoadingServiceTests.testMaxCachedLimitReached(ModelLoadingServiceTests.java:193)
Actually, there were zero interactions with this mock.
Mockito seems a bit sassy
run elasticsearch-ci/1 |
d6ae5a4
to
8ea25cc
Compare
run elasticsearch-ci/2 |
3 similar comments
run elasticsearch-ci/2 |
run elasticsearch-ci/2 |
run elasticsearch-ci/2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ran each test over 10k times.
even when tests are green, Jenkins finds, uh, a way. :)
I think this is safe to merge.
In the test after the first load event is is not known which models are cached as loading a later one will evict an earlier one and the order is not known. The models could have been loaded 1 or 2 times not exactly twice
In the test after the first load event is is not known which models are cached as loading a later one will evict an earlier and the order is not known. The first fix in #55008 recognised this error but got the counting wrong. The models could have been loaded 1 or 2 times not exactly twice