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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group4/tests/alerting/alerts·ts - alerting api integration security and spaces enabled - Group 4 Alerts alerts alerts connector adapters should use connector adapters correctly on system actions #198388

Open
kibanamachine opened this issue Oct 30, 2024 · 4 comments · May be fixed by #198396
Open

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group4/tests/alerting/alerts·ts - alerting api integration security and spaces enabled - Group 4 Alerts alerts alerts connector adapters should use connector adapters correctly on system actions #198388

kibanamachine opened this issue Oct 30, 2024 · 4 comments · May be fixed by #198396
Assignees
@mikecote
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 Oct 30, 2024 •
edited
Loading

A test failed on a tracked branch

Error: expected 2 to equal 1
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at validateSystemActionEventLog (alerts.ts:2083:30)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Context.<anonymous> (alerts.ts:1909:9)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 30, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 30, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Oct 30, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 30, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@mikecote mikecote self-assigned this Oct 30, 2024
@mikecote mikecote linked a pull request Oct 30, 2024 that will close this issue
Draft
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikecote mikecote

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

Successfully merging a pull request may close this issue.

Fix flaky connector adapters test mikecote/kibana
3 participants
@mikecote @elasticmachine @kibanamachine