Flaky test: tests/sentry/snuba/test_errors.py::ErrorsQueryIntegrationTest::test_error_handled_alias
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/snuba/test_errors.py::ErrorsQueryIntegrationTest::test_error_handled_alias`
Sentry sha: 06f4fc3ff37f1db5884793078c11b706fa99c8f3
Run: https://github.com/getsentry/sentry/actions/runs/22287603655
```
[1m[31mtests/sentry/snuba/test_errors.py[0m:841: in test_error_handled_alias
assert len(data) == len(expected_data)
[1m[31mE AssertionError: assert 4 == 3[0m
[1m[31mE + where 4 = len([{'error.handled': 0}, {'error.handled': 0}, {'error.handled': 1}, {'error.handled': 1}])[0m
[1m[31mE + and 3 = len([0, 1, 1])[0m
```
Contributor guide
Research direction
Start with tests/sentry/snuba/test_errors.py::ErrorsQueryIntegrationTest::test_error_handled_alias and reproduce the failure from the linked GitHub Actions run. Inspect why the query returns four error.handled records while the test expects three; done means the test passes reliably with the intended result.
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
- 25/100