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.

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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/run_soon·ts - alerting api integration spaces only Alerting runSoon should successfully run rule where scheduled task id is same as rule id #142564

Closed
kibanamachine opened this issue Oct 4, 2022 · 8 comments · Fixed by #142652
Assignees
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 4, 2022

A test failed on a tracked branch

Error: expected 200 to sort of equal 204
    at Assertion.assert (node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.eql (node_modules/@kbn/expect/expect.js:244:8)
    at Context.<anonymous> (x-pack/test/alerting_api_integration/spaces_only/tests/alerting/run_soon.ts:58:41)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16) {
  actual: '200',
  expected: '204',
  showDiff: true
}

First failure: CI Build - main

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

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

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

New failure: CI Build - 8.5

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.5

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@jbudz
Copy link
Member

jbudz commented Oct 4, 2022

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 7e01603
8.5: cdd54ea

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

Repository owner moved this from In Review to Done in AppEx: ResponseOps - Execution & Connectors Oct 5, 2022
WafaaNasr pushed a commit to WafaaNasr/kibana that referenced this issue Oct 11, 2022
WafaaNasr pushed a commit to WafaaNasr/kibana that referenced this issue Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants