[RAM] Fix Snooze And Unsnooze Tests #163632
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jcger
changed the title
jcger
added
release_note:skip
|
Pinging @elastic/response-ops (Team:ResponseOps) |
|
lets verify with flaky test runner for these 2 tests 😀 |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
|
Flaky test runner succeeded |
guskovaue
approved these changes
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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