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/22426766678
```
[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 the failure from GitHub Actions run 22426766678. Reproduce the assertion that len(rows) is 2 instead of 3, then identify why the expected replay row is missing. Done means the test passes reliably with the intended three rows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100