-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] InferenceIngestIT.testPipelineIngest and testPathologicalPipelineCreationAndDeletion failures #61564
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 (:ml) |
This is still failing in the same way:
The build scan for that is: https://gradle-enterprise.elastic.co/s/pk6orftvu2us2 |
another one https://gradle-enterprise.elastic.co/s/h5omv5t3fhc36 |
benwtrent
added a commit
that referenced
this issue
Dec 3, 2020
…nts (#65774) Looking over the failure history, it is always the cache miss count that is off. This is mostly ok as all the failures had indicated that there were indeed cache failures and every one of them were fence-post errors. Opting to make the cache miss count check lenient as other stats checked verify consistency. closes #61564
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Dec 3, 2020
…nts (elastic#65774) Looking over the failure history, it is always the cache miss count that is off. This is mostly ok as all the failures had indicated that there were indeed cache failures and every one of them were fence-post errors. Opting to make the cache miss count check lenient as other stats checked verify consistency. closes elastic#61564
benwtrent
added a commit
that referenced
this issue
Dec 3, 2020
…nts (#65774) (#65815) Looking over the failure history, it is always the cache miss count that is off. This is mostly ok as all the failures had indicated that there were indeed cache failures and every one of them were fence-post errors. Opting to make the cache miss count check lenient as other stats checked verify consistency. closes #61564
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/2kdpwkkrjc6r4
Repro line:
Reproduces locally?:
No
Applicable branches:
Failure history:
These two tests seem only fail for v7 branches. It failed 8 times within last 60 days according to build-stats.
When they fail, there are always failures of `ClassificationIT in the same build scan with "ClusterHealthResponse has timed out" error. Maybe they are related, like one is the cause of the other.
I also noticed we have a previous issue (#54786) for testPipelineIngest but the failure message is different. So I am opening a new issue.
Failure excerpt:
The text was updated successfully, but these errors were encountered: