You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #122627 Kibana v7.last must be compatible with ES v8.x.
The Operations team added a CI check to verify the compatibility on CI.
Some functional tests using deprecated API (removed in v8.0) started failing. You can find the actual list of failing test suites here #122962 fixed most of the common problems. We need someone with deeper domain knowledge to fix the remaining test failures. Nore that tests on Kibana 7.last branch are executed in two different setups:
the standard CI job: Kibana v7.last <--> Elasticsearch v7.last
the major version compatibility check CI job: Kibana v7.last <--> Elasticsearch v8.x
Thus, the test on the 7.17 branch must be compatible with both modes.
This umbrella issue keeps track of the known test failures that need to be addressed by code owners:
After #122627 Kibana
v7.last
must be compatible with ESv8.x
.The Operations team added a CI check to verify the compatibility on CI.
Some functional tests using deprecated API (removed in
v8.0
) started failing. You can find the actual list of failing test suites here#122962 fixed most of the common problems. We need someone with deeper domain knowledge to fix the remaining test failures. Nore that tests on Kibana
7.last
branch are executed in two different setups:standard
CI job: Kibanav7.last
<--> Elasticsearchv7.last
major version compatibility check
CI job: Kibanav7.last
<--> Elasticsearchv8.x
Thus, the test on the
7.17
branch must be compatible with both modes.This umbrella issue keeps track of the known test failures that need to be addressed by code owners:
Some failures are due to our CI environment and not a bug in Kibana:
The text was updated successfully, but these errors were encountered: