[Response Ops][Task Manager] Fix skipped task manager health test #144558
Assignees
Labels
Feature:Task Manager
skipped-test
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
ymao1
added
skipped-test
Feature:Task Manager
Team:ResponseOps
|
Pinging @elastic/response-ops (Team:ResponseOps) |
ymao1
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
|
Wait until PR merges |
|
Looks like we need to update the schedule interval aggregation to return more than 10 buckets. |
ymao1
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
ymao1
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
Repository owner
moved this from In Review
to Done
in AppEx: ResponseOps - Execution & Connectors
Nov 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This PR adding a new task type was seeing failures in the task manager functional test in
x-pack/test/plugin_api_integration/test_suites/task_manager/health_route.ts. Took a quick look and I believe that with the addition of the new task type, the number of tasks that are being run when starting up the FT is delaying the run of the sample task, which affects the expected health output. In order to unblock their PR, we skipped the test and this issue is for resolving the skipped test.The text was updated successfully, but these errors were encountered: