Flaky test: tests/sentry/services/eventstore/test_models.py::EventTest::test_snuba_data
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/services/eventstore/test_models.py::EventTest::test_snuba_data`
Sentry sha: 2597189bd40bd108bd7ec710a885fc0cc3e38548
Run: https://github.com/getsentry/sentry/actions/runs/22282680173
```
[1m[31mtests/sentry/services/eventstore/test_models.py[0m:255: in test_snuba_data
assert event_from_nodestore.timestamp == event_from_snuba.timestamp
[1m[31mE AssertionError: assert '2026-02-22T18:26:34+00:00' == '2026-02-22T1....099000+00:00'[0m
[1m[31mE [0m
[1m[31mE - 2026-02-22T18:27:34.099000+00:00[0m
[1m[31mE ? ^ -------[0m
[1m[31mE + 2026-02-22T18:26:34+00:00[0m
[1m[31mE ? ^[0m
```
Contributor guide
Research direction
Start with tests/sentry/services/eventstore/test_models.py::EventTest::test_snuba_data and reproduce the failure using the linked GitHub Actions run or the recorded Sentry SHA. Investigate why the nodestore and Snuba event timestamps differ in both seconds and microseconds. Done means the test passes reliably and preserves the intended timestamp comparison.
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
- 42/100