Flaky test: tests/sentry/issues/test_run.py::TestBatchedOccurrenceConsumer::test_issue_multiple_status_changes
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/issues/test_run.py::TestBatchedOccurrenceConsumer::test_issue_multiple_status_changes`
Sentry sha: 3ae13ebdfdfbfd0d73e8a04d635b9ae4d95251de
Run: https://github.com/getsentry/sentry/actions/runs/22294923574
```
[1m[31mtests/sentry/issues/test_run.py[0m:518: in test_issue_multiple_status_changes
assert mock_process_occurrence_group.call_count == 1
[1m[31mE AssertionError: assert 2 == 1[0m
[1m[31mE + where 2 = .call_count[0m
```
Contributor guide
Research direction
Start with tests/sentry/issues/test_run.py::TestBatchedOccurrenceConsumer::test_issue_multiple_status_changes and reproduce the failure using the linked GitHub Actions run as context. Inspect why process_occurrence_group is called twice instead of once, then confirm the test passes consistently with the expected call count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100