Flaky test: tests/sentry/replays/test_data_export.py::test_replay_data_export
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/test_data_export.py::test_replay_data_export
Sentry sha: c5a059afe94a41739cafe1be0cbb7bcaea728b8f
Run: https://github.com/getsentry/sentry/actions/runs/22266451700
[1m[31mtests/sentry/replays/test_data_export.py[0m:50: in test_replay_data_export
assert store_rows.called
[1m[31mE AssertionError: assert False[0m
[1m[31mE + where False = <MagicMock name='save_to_storage' id='140474292381616'>.called[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 by running tests/sentry/replays/test_data_export.py::test_replay_data_export and read the failure at line 50, where save_to_storage is expected to have been called. Inspect the test and its replay data export path to determine why the call is skipped or missed. Done means the test passes reliably and the storage call assertion succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100