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 - Alerting - group4.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group4/snooze·ts - Alerting snooze should clear the snooze after it expires #159076

Closed
kibanamachine opened this issue Jun 5, 2023 · 10 comments · Fixed by #159233, #159610 or #163632
Closed

Failing test: X-Pack Alerting API Integration Tests - Alerting - group4.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group4/snooze·ts - Alerting snooze should clear the snooze after it expires #159076

kibanamachine opened this issue Jun 5, 2023 · 10 comments · Fixed by #159233, #159610 or #163632
Assignees
@jcger
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

kibanamachine commented Jun 5, 2023 •
edited
Loading

A test failed on a tracked branch

Error: expected [] to sort of equal [ { duration: 1000,
    rRule: 
     { dtstart: '2023-06-05T23:05:13.903Z',
       tzid: 'UTC',
       count: 1 } } ]
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Context.<anonymous> (snooze.ts:369:47)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (wrap_function.js:73:16) {
  actual: '[]',
  expected: '[\n' +
    '  {\n' +
    '    "duration": 1000\n' +
    '    "rRule": {\n' +
    '      "count": 1\n' +
    '      "dtstart": "2023-06-05T23:05:13.903Z"\n' +
    '      "tzid": "UTC"\n' +
    '    }\n' +
    '  }\n' +
    ']',
  showDiff: true
}

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jun 5, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Jun 5, 2023
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jun 5, 2023
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jun 5, 2023
@XavierM XavierM moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Rules & Alerts Management Jun 6, 2023
@Zacqary Zacqary mentioned this issue Jun 6, 2023
Closed
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@Zacqary Zacqary mentioned this issue Jun 7, 2023
Merged
@mistic
Copy link
Member

mistic commented Jun 7, 2023

Skipped.

main: fd95b37

mistic added a commit that referenced this issue Jun 7, 2023
@mistic
skip flaky suite (#159076)
fd95b37
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

Zacqary added a commit that referenced this issue Jun 8, 2023
@Zacqary @kibanamachine
[RAM] Fix flaky expiring snooze test (reopen) (#159233)
5bb0a05 
## Summary

Closes #159076

Wraps a flaky bit of test in retry.try

Second attempt to merge #159138 after that one inexplicably got its git
all in a twist or something

---------

Co-authored-by: Kibana Machine <[email protected]>
Zacqary added a commit to Zacqary/kibana that referenced this issue Jun 8, 2023
@Zacqary
Revert "skip flaky suite (elastic#159076)"
c25a6be 
This reverts commit fd95b37.
@kibanamachine kibanamachine reopened this Jun 13, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

XavierM pushed a commit that referenced this issue Jun 14, 2023
@Zacqary
[RAM] Increase flaky test snooze duration to 10s (#159610)
e58aced 
## Summary

Fix #159076

Increases snooze expiry duration in hopes CI will catch it before it
disappears.

Passes flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2382
@mikecote
Copy link
Contributor

Re-opening as the test is still skipped.

@mikecote mikecote reopened this Jul 24, 2023
@XavierM XavierM assigned guskovaue and jcger and unassigned guskovaue Aug 8, 2023
@XavierM XavierM moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Rules & Alerts Management Aug 8, 2023
@jcger jcger mentioned this issue Aug 11, 2023
Merged
@jcger jcger moved this from Todo to In Progress in AppEx: ResponseOps - Rules & Alerts Management Aug 11, 2023
@jcger jcger moved this from In Progress to In Review in AppEx: ResponseOps - Rules & Alerts Management Aug 11, 2023
jcger added a commit that referenced this issue Aug 29, 2023
@jcger
[RAM] Fix Snooze And Unsnooze Tests (#163632)
1543750 
## Summary

Closes #159076
Unskipping snooze test
Activating unsnooze test

The problem began with setting dtstart well ahead of the test
initiation, causing the snooze period to pass before the test even
started
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcger jcger

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
No open projects
AppEx: ResponseOps - Rules & Alerts Management
Status: Done
Milestone
No milestone
8 participants
@Zacqary @mikecote @mistic @bhavyarm @elasticmachine @jcger @guskovaue @kibanamachine