Flaky test: tests/sentry/replays/test_data_export.py::test_replay_data_export_no_replay_data
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/replays/test_data_export.py::test_replay_data_export_no_replay_data`
Sentry sha: abdb2eeccb973e9b33600d0fb95e18b12b995415
Run: https://github.com/getsentry/sentry/actions/runs/22208448055
```
[1m[31mtests/sentry/replays/test_data_export.py[0m:145: in test_replay_data_export_no_replay_data
assert not store_rows.called
[1m[31mE AssertionError: assert not True[0m
[1m[31mE + where True = .called[0m
```
Contributor guide
Research direction
Start with tests/sentry/replays/test_data_export.py::test_replay_data_export_no_replay_data and reproduce the failure from the linked GitHub Actions run. Trace why save_to_storage is called when no replay data exists, then confirm the test passes consistently without that call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100