Flaky test: tests/sentry/uptime/endpoints/test_organization_uptime_stats.py::OrganizationUptimeStatsEndpointWithEAPTests::test_missing_ok_checks_around_downtime
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/uptime/endpoints/test_organization_uptime_stats.py::OrganizationUptimeStatsEndpointWithEAPTests::test_missing_ok_checks_around_downtime`
Sentry sha: 4a80dec864917198998a489a30e28e2fbdcef252
Run: https://github.com/getsentry/sentry/actions/runs/22426768098
```
[1m[31mtests/sentry/uptime/endpoints/test_organization_uptime_stats.py[0m:284: in test_missing_ok_checks_around_downtime
timeline = data[str(detector.id)]
[1m[31mE KeyError: '3037'[0m
```
Contributor guide
Research direction
Start by running tests/sentry/uptime/endpoints/test_organization_uptime_stats.py::OrganizationUptimeStatsEndpointWithEAPTests::test_missing_ok_checks_around_downtime and review the failure at line 284. Compare repeated runs with the reported Sentry SHA and trace why the detector timeline is absent. Done means the test passes reliably without the KeyError.
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
- 38/100