Flaky test: tests/sentry/replays/integration/test_data_export.py::test_export_replay_row_set
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/replays/integration/test_data_export.py::test_export_replay_row_set`
Sentry sha: 4a80dec864917198998a489a30e28e2fbdcef252
Run: https://github.com/getsentry/sentry/actions/runs/22426767202
```
[1m[31mtests/sentry/replays/integration/test_data_export.py[0m:83: in test_export_replay_row_set
assert len(rows) == 3
[1m[31mE AssertionError: assert 2 == 3[0m
[1m[31mE + where 2 = len([['replay_id', 'debug_id', 'count_info_events', 'count_warning_events', 'count_error_events', 'info_id', ...], ['0dbda...409-aa32b241563d', '00000000-0000-0000-0000-000000000000', '0', '0', '0', '00000000-0000-0000-0000-000000000000', ...]])[0m
```
Contributor guide
Research direction
Start with tests/sentry/replays/integration/test_data_export.py::test_export_replay_row_set and reproduce the failure from the linked GitHub Actions run. Inspect why the test receives two rows instead of the expected three. Done means the replay data export test passes reliably with the intended row set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100