test(replays): fix flaky test_export_replay_row_set #113742
Merged
Conversation
…etime(2025,1,1) with utcnow()-1h so rows stay in query window
joshuarli
changed the title
ryan953
approved these changes
Apr 22, 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
2 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.
fixes https://sentry.sentry.io/issues/6918185853/events/?alert_rule_id=14448768&project=2423079 / SENTRY-TESTS-19MW
t0was hardcoded todatetime(2025, 1, 1), so replay rows written at that timestamp fell outside the export query window once wall-clock time passed that date, causingassert 2 == 3failures.Replaced with
utcnow() - 1 hourso the test data is always recent relative to when the test runs.