-
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 test: Serverless Observability Examples Functional Tests.x-pack/test_serverless/functional/test_suites/common/examples/partial_results/index·ts - serverless examples UI Partial Results Example "before all" hook for "should trace mouse events" #165563
Comments
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: def8b65 |
## Summary This PR unskips the partial results Serverless tests. I ran 100x flaky test runs against each project type to confirm they should no longer be flaky. Flaky test runs: - x100 (`.only`): https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3114 - x100 Search: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3121 - x100 O11y: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3147 - x100 Security: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3156 Resolves #165563. Resolves #165612. Resolves #165763. ### Checklist - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
New failure: CI Build - main |
New failure: CI Build - main |
Closing this for now because the recent failures are unrelated auth errors. |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: