Flaky test: tests/sentry/tasks/test_post_process.py::PostProcessGroupErrorTest::test_issue_owners_should_ratelimit
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/tasks/test_post_process.py::PostProcessGroupErrorTest::test_issue_owners_should_ratelimit
Sentry sha: 02e8ded902342f5b18db32c91f8f4f174afc4551
Run: https://github.com/getsentry/sentry/actions/runs/22243431580
[1m[31mtests/sentry/tasks/test_post_process.py[0m:1490: in test_issue_owners_should_ratelimit
mock_incr.assert_any_call(
[1m[31m/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/unittest/mock.py[0m:1048: in assert_any_call
raise AssertionError(
[1m[31mE AssertionError: incr('sentry.task.post_process.handle_owner_assignment.ratelimited') call not found[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/tasks/test_post_process.py::PostProcessGroupErrorTest::test_issue_owners_should_ratelimit and review the failure from the linked GitHub Actions run. Reproduce the test and inspect why the expected ratelimit metric call is not consistently recorded. Done means the test passes reliably and still verifies the intended metric call.
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
- Needs clarification
- Newbie friendliness
- 35/100