-
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: Explore - Network Integration Tests - Serverless Env - Complete Tier.x-pack/test/security_solution_api_integration/test_suites/explore/network/trial_license_complete_tier/tests/network_top_n_flow·ts - @ess @serverless SecuritySolution Explore Network Network Top N Flow With filebeat should get Source NetworkTopNFlow data with bytes_in descending sort #199363
Labels
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Nov 7, 2024
Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore) |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped. main: 00d14e5 |
New failure: kibana-on-merge - main |
mbondyra
pushed a commit
to mbondyra/kibana
that referenced
this issue
Nov 8, 2024
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Nov 8, 2024
Merged
11 tasks
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Nov 11, 2024
…dation errors in tests (elastic#199539) ## Summary This PR fixes an issue introduced in elastic#196962 where search strategy polling requests sent from some integration tests were missing necessary body parameters, resulting in validation errors and test failures. This issue was not caught by CI in the original PR because it only occurs when a search request runs slow enough to return partial results (and therefore requires polling), which is not common in test runs. Fixes elastic#199537 Fixes elastic#199499 Fixes elastic#199460 Fixes elastic#199449 Fixes elastic#199412 Fixes elastic#199410 Fixes elastic#199394 Fixes elastic#199379 Fixes elastic#199372 Fixes elastic#199363 Fixes elastic#199541 Fixes elastic#199446 Fixes elastic#199433 Fixes elastic#199432 Fixes elastic#199381 Fixes elastic#199369 Fixes elastic#199364 Flaky test runner x200: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7362. ### 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 - [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 - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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#_add_your_labels) - [ ] This will appear in the **Release Notes** and follow the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: