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.

Sign up for GitHub

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

Jump to bottom

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group1/tests/alerting/backfill/find·ts - alerting api integration security and spaces enabled Alerts - Group 1 alerts backfill rule runs find backfill space_1_all_with_restricted_fixture at space1 should handle finding backfill requests with query string appropriately #198631

Closed
kibanamachine opened this issue Nov 1, 2024 · 1 comment · Fixed by #199562
Closed

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group1/tests/alerting/backfill/find·ts - alerting api integration security and spaces enabled Alerts - Group 1 alerts backfill rule runs find backfill space_1_all_with_restricted_fixture at space1 should handle finding backfill requests with query string appropriately #198631

kibanamachine opened this issue Nov 1, 2024 · 1 comment · Fixed by #199562
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: expected 2 to sort of equal 1
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Context.<anonymous> (find.ts:552:65)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:74:16) {
  actual: '2',
  expected: '1',
  showDiff: true
}

First failure: kibana-on-merge - 8.16
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 1, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 1, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Nov 1, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 1, 2024
@ymao1 ymao1 mentioned this issue Nov 8, 2024
Merged
@ymao1 ymao1 closed this as completed in 51ac51f Nov 13, 2024
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Nov 13, 2024
@ymao1
Fixing flaky tests (elastic#199562)
1a548d0 
Resolves elastic#196226
Resolves elastic#197352
Resolves elastic#198631
Resolves elastic#199722
Resolves elastic#199351
Resolves elastic#199580

## Summary

* Fixes flaky `find` test that relied on relative dates to use a fixed
offset in the find query params. This closes multiple issues because it
is a security and spaces test that uses the same test for different
user/space scenarios
* Fixes flaky `schedule` test that was checking AAD on an
`ad_hoc_run_param` object after backfill was complete and the SO was
completed. Added artificial delay to rule execution so the backfill
doesn't run as quickly.

Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 51ac51f)
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Nov 18, 2024
@ymao1 @elasticmachine @CAWilson94
Fixing flaky tests (elastic#199562)
b48c59e 
Resolves elastic#196226
Resolves elastic#197352
Resolves elastic#198631
Resolves elastic#199722
Resolves elastic#199351
Resolves elastic#199580

## Summary

* Fixes flaky `find` test that relied on relative dates to use a fixed
offset in the find query params. This closes multiple issues because it
is a security and spaces test that uses the same test for different
user/space scenarios
* Fixes flaky `schedule` test that was checking AAD on an
`ad_hoc_run_param` object after backfill was complete and the SO was
completed. Added artificial delay to rule execution so the backfill
doesn't run as quickly.

Co-authored-by: Elastic Machine <[email protected]>
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Nov 18, 2024
@ymao1 @elasticmachine @CAWilson94
Fixing flaky tests (elastic#199562)
1a7132f 
Resolves elastic#196226
Resolves elastic#197352
Resolves elastic#198631
Resolves elastic#199722
Resolves elastic#199351
Resolves elastic#199580

## Summary

* Fixes flaky `find` test that relied on relative dates to use a fixed
offset in the find query params. This closes multiple issues because it
is a security and spaces test that uses the same test for different
user/space scenarios
* Fixes flaky `schedule` test that was checking AAD on an
`ad_hoc_run_param` object after backfill was complete and the SO was
completed. Added artificial delay to rule execution so the backfill
doesn't run as quickly.

Co-authored-by: Elastic Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing flaky tests ymao1/kibana
2 participants
@elasticmachine @kibanamachine