-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing ES Promotion: Several Security Solutions Suites #125851
Comments
Merging into a one issue along with other failures. |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt) |
@paul-tavares @dasansol92 - It looks like our tests are failing to install the Endpoint package at startup after the ES upgrade. A couple recurring errors I'm seeing: |
The endpoint specific tests have been un-skiped: #125963 Others are being worked by the @elastic/security-detections-response team |
I have also skipped these tests from the cloud and platform runs: |
…of ES promotion failures (elastic#125963) Fixes some issues from elastic#125851
The tests were failing and flake because of this issue: This PR is un-skipping them as that should be fixed now: Once that builds I will merge it and we should be ok to close this ticket. |
…126294) ## Summary Increases the timeouts from 2 minutes to now 5 minutes and unskips the detection tests. If any of the tests fail consistently then I will skip just those individual tests instead of the whole suit. See #125851 and elastic/elasticsearch#84256 This could cause issues with: #125319 If so, then we will have to deal with the cloud based tests in a different way but in reality we need the extra time as some test cases do take a while to run on CI. This also: * Removes skips around code that have been in there for a while and adds documentation to the parts that are left over. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
🎉🎉🎉 |
…lastic#126294) ## Summary Increases the timeouts from 2 minutes to now 5 minutes and unskips the detection tests. If any of the tests fail consistently then I will skip just those individual tests instead of the whole suit. See elastic#125851 and elastic/elasticsearch#84256 This could cause issues with: elastic#125319 If so, then we will have to deal with the cloud based tests in a different way but in reality we need the extra time as some test cases do take a while to run on CI. This also: * Removes skips around code that have been in there for a while and adds documentation to the parts that are left over. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Several Security Solution tests
These failures are preventing the promotion of the current Elasticsearch nightly snapshot.
For more information on the Elasticsearch snapshot promotion process including how to reproduce using the unverified nightly ES build: https://www.elastic.co/guide/en/kibana/master/development-es-snapshots.html
Failed promotion jobs:
NOTE: Turns out these are only a sample of the failures, I'm giving up trying to skip only what's necessary and I've skipped all the neighbor suites to the ones listed above. I recommend searching for all the
// FAILING ES PROMOTION: https://github.com/elastic/kibana/issues/125851
comments, removing them and their associated skips, and then running the modified suites locally or in a PR once themain
es snapshot is updated to get these working with the new snapshot.Some of the Failures:
The text was updated successfully, but these errors were encountered: