Flaky test: tests/sentry/replays/integration/test_data_export.py::test_export_replay_row_set
Open
Nobody has claimed this yet.
flaky-test
Tests
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
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/22426765699
[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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tests/sentry/replays/integration/test_data_export.py::test_export_replay_row_set and reproduce the failure using the linked GitHub Actions run or the recorded Sentry SHA. Investigate why the export produces two rows instead of three, then make the test reliable and verify that it passes consistently.
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
- Mostly clear
- Newbie friendliness
- 45/100