test(escalating): Skip flaky test_is_forecast_out_of_range#113951
Merged
test(escalating): Skip flaky test_is_forecast_out_of_range#113951
Conversation
The test intermittently fails in CI with `(False, None) != (True, 1)`. Skip it to unblock CI, matching the adjacent test_is_escalating_two_weeks which is skipped for the same reason. Co-Authored-By: Claude <noreply@anthropic.com> Agent transcript: https://claudescope.sentry.dev/share/OTrFh2EhYKCbafh2eOy5N-lC5tnY3YsbpecEEVc-0rc
cmanallen
approved these changes
Apr 24, 2026
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b0d36eb. Configure here.
| # Events are aggregated in the hourly count query by date rather than the last 24hrs | ||
| assert get_group_hourly_count_snuba(group) == (1, False) | ||
|
|
||
| @pytest.mark.skip(reason="flaky") |
Contributor
There was a problem hiding this comment.
Missing issue tracker reference in skip reason
Low Severity
The skip reason "flaky" is missing an issue tracker reference. Every other @pytest.mark.skip in this file follows the pattern "flaky: #NNNNN" (e.g., "flaky: #94622", "flaky: #93732", "flaky: #95139"). Without a linked issue number, it becomes harder to track when and why the test was skipped, and to know when it can be re-enabled.
Reviewed by Cursor Bugbot for commit b0d36eb. Configure here.
joshuarli
approved these changes
Apr 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Skip
DailyGroupCountsEscalating.test_is_forecast_out_of_range, whichintermittently fails in CI with
(False, None) != (True, 1).Matches the adjacent
test_is_escalating_two_weeks, which is alreadyskipped as flaky (#94622). Filing as a follow-up so the underlying
escalating-forecast flake can be investigated separately without
keeping CI red.
Agent transcript: https://claudescope.sentry.dev/share/C7E02BqBL8OBDqmebTBImGr1Ina3Tlk4fD03tixw6NM