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: Serverless Search API Integration Tests - Common Group 1.x-pack/test_serverless/api_integration/test_suites/common/alerting/rules·ts - Alerting APIs Alerting rules should retry when appropriate #194226

Open
kibanamachine opened this issue Sep 26, 2024 · 1 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)

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: retry.tryWithRetries reached the limit of attempts waiting for 'Alerting API - waiting.waitForAllTasks, retryOptions: {"retryCount":10,"retryDelay":1000}': 10 out of 10
Error: No hits found
    at alerting_api.ts:856:21
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:30:15)
    at retryForSuccess (retry_for_success.ts:99:21)
    at RetryService.tryWithRetries (retry.ts:113:12)
    at Object.waitForAllTasks (alerting_api.ts:814:16)
    at Context.<anonymous> (rules.ts:314:20)
    at Object.apply (wrap_function.js:74:16)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:75:7)
    at RetryService.tryWithRetries (retry.ts:113:12)
    at Object.waitForAllTasks (alerting_api.ts:814:16)
    at Context.<anonymous> (rules.ts:314:20)
    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 Sep 26, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 26, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Sep 26, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 26, 2024
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
None yet
Development

No branches or pull requests

2 participants