-
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
[Search] test: fix and rework es3 connectors ftr #205971
base: main
Are you sure you want to change the base?
[Search] test: fix and rework es3 connectors ftr #205971
Conversation
I'll run the flakey test runner once I get a clean CI run, and before merging this. |
aba3953
to
304fd93
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.
Thank you so much for looking into this! 🚢
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#7683[❌] x-pack/test_serverless/functional/test_suites/search/config.ts: 3/30 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#7699[❌] x-pack/test_serverless/functional/test_suites/search/config.ts: 0/25 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#7700[❌] x-pack/test_serverless/functional/test_suites/search/config.ts: 0/25 tests passed. |
8c860eb
to
87504c7
Compare
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#7731[❌] x-pack/test_serverless/functional/test_suites/search/config.ts: 0/25 tests passed. |
87504c7
to
53d8c82
Compare
⏳ Build in-progress, with failures
Failed CI StepsTest Failures
History
|
Closes #203477
Closes #203462
Summary
This should 🤞 resolved failures with the ES3 Connectors FTRs that caused them to be skipped.
Checklist