-
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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/disable·ts - alerting api integration spaces only Alerting disable should handle disable rule request appropriately #141864
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
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Sep 26, 2022
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Sep 26, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: CI Build - main |
/skip |
Skipped main: 5ff2232 |
kibanamachine
added a commit
that referenced
this issue
Oct 4, 2022
mikecote
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Oct 4, 2022
ymao1
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Oct 4, 2022
This was referenced Oct 4, 2022
ymao1
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
Oct 5, 2022
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
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - 8.5 |
mikecote
moved this from Done
to Awaiting Triage
in AppEx: ResponseOps - Execution & Connectors
Oct 25, 2022
New failure: CI Build - main |
/skip |
Skipped main: 1a1ee54 |
kibanamachine
added a commit
that referenced
this issue
Nov 3, 2022
doakalexi
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Nov 4, 2022
ersin-erdal
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Nov 9, 2022
ymao1
added a commit
that referenced
this issue
Dec 21, 2022
Resolves #145316, #141849, #141864 ## Summary Adds a retry on conflict error to the saved objects bulk update call made by task manager. Errors are returned by the saved object client inside an array (with a success response). Previously, we were not inspecting the response array, just returning the full data. With this PR, we are inspecting the response array specifically for conflict errors and retrying the update for just those tasks. This `bulkUpdate` function is used both internally by task manager and externally by the rules client. I default the number of retries to 0 for bulk updates from the task manager in order to preserve existing behavior (and in order not to increase the amount of time it takes for task manager to run) but use 3 retries when used externally. Also unskipped the two flaky disable tests and ran them through the flaky test runner 400 times with no failures. * https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1652 * https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1653 * https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1660 * https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1661 Co-authored-by: Kibana Machine <[email protected]>
Fixed with #147808 |
Repository owner
moved this from In Progress
to Done
in AppEx: ResponseOps - Execution & Connectors
Dec 21, 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)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: