Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts_list·ts - Actions and Triggers app alerts list should update alert list on the search clear button click #213311

Open
kibanamachine opened this issue Mar 6, 2025 · 10 comments
Open

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts_list·ts - Actions and Triggers app alerts list should update alert list on the search clear button click #213311

kibanamachine opened this issue Mar 6, 2025 · 10 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Mar 6, 2025 •
edited
Loading

A test failed on a tracked branch

Error: expected 2 to equal 1
    at Assertion.assert (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1741241572155610073/elastic/kibana-es-forward-compatibility-testing/kibana/node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.equal (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1741241572155610073/elastic/kibana-es-forward-compatibility-testing/kibana/node_modules/@kbn/expect/expect.js:227:8)
    at Context.<anonymous> (test/functional_with_es_ssl/apps/triggers_actions_ui/alerts_list.ts:117:39)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1741241572155610073/elastic/kibana-es-forward-compatibility-testing/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:78:16)

First failure: kibana-es-forward-compatibility-testing - 7.17
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Mar 6, 2025
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 6, 2025
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Mar 6, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 6, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing - 7.17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @kibanamachine