-
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: Jest Integration Tests.x-pack/plugins/task_manager/server/integration_tests - capacity based claiming should claim tasks to full capacity #191117
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped main: 53b5d7c |
New failure: kibana-on-merge - main |
…r/server/integration_tests - capacity based claiming should claim tasks to full capacity (#191125) Resolves #191117 ## Summary Made the following changes to reduce flakiness: * Set the `runAt` date slightly in the past * Ensured the partitions are properly set when scheduling the task After making these changes, was able to run the capacity claiming tests [50](https://buildkite.com/elastic/kibana-pull-request/builds/232049#0191be3e-9834-4a8f-b0bf-f84a15cab89a) & [65](https://buildkite.com/elastic/kibana-pull-request/builds/232106) times without failing.
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped main: ef6f3c7 |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
…r/server/integration_tests - capacity based claiming should claim tasks to full capacity (#192519) Resolves #191117 This test became flaky again after merging this PR #192261 which changes Kibana to claim tasks against all partitions when the partitions have not yet been assigned. This was due to setting the `runAt` value to `now-1000` which means that all injected tasks were immediately overdue and claimable as soon as possible, which means they might get claimed in different claim cycles. This PR changes the `runAt` value to `now + 5000` so injected tasks won't be claimed until they're all injected so they should be claimed in one cycle. Copied this test 60 times and was able to run the integration tests twice (so 120 times total) with no failures. * https://buildkite.com/elastic/kibana-pull-request/builds/233196#0191dd0b-fe03-40cf-9fab-b211dd662993 * https://buildkite.com/elastic/kibana-pull-request/builds/233236#0191dd94-8010-4b3c-988d-6e7d5655f989
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped. main: b196452 |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: