Flaky test: tests/sentry/seer/explorer/test_explorer_client.py::TestSeerExplorerClientPushChanges::test_push_changes_polls_until_complete
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/seer/explorer/test_explorer_client.py::TestSeerExplorerClientPushChanges::test_push_changes_polls_until_complete
Sentry sha: 5d2fb55dc4851f3fed1a58b2eabfdb4d41c73cce
Run: https://github.com/getsentry/sentry/actions/runs/22284911236
[1m[31mtests/sentry/seer/explorer/test_explorer_client.py[0m:703: in test_push_changes_polls_until_complete
assert mock_sleep.call_count == 1
[1m[31mE AssertionError: assert 627 == 1[0m
[1m[31mE + where 627 = <MagicMock name='sleep' id='139828906830752'>.call_count[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/seer/explorer/test_explorer_client.py::TestSeerExplorerClientPushChanges::test_push_changes_polls_until_complete and review the failure from the linked GitHub Actions run. Determine why mock_sleep.call_count is 627 instead of 1, then make the polling test reliable and rerun the test to verify 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
- 35/100