Flaky test: tests/sentry/taskworker/test_config.py::test_taskworker_schedule_parameters
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/taskworker/test_config.py::test_taskworker_schedule_parameters
Sentry sha: 2597189bd40bd108bd7ec710a885fc0cc3e38548
Run: https://github.com/getsentry/sentry/actions/runs/22282683583
[1m[31mtests/sentry/taskworker/test_config.py[0m:59: in test_taskworker_schedule_parameters
task = taskregistry.get_task(namespace, taskname)
[1m[31msrc/sentry/taskworker/registry.py[0m:241: in get_task
return self.get(namespace).get(task)
[1m[31msrc/sentry/taskworker/registry.py[0m:67: in get
raise KeyError(f"No task registered with the name {name}. Check your imports")
[1m[31mE KeyError: 'No task registered with the name sentry.tasks.send_ping. Check your imports'[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 by running tests/sentry/taskworker/test_config.py::test_taskworker_schedule_parameters and read the failure at src/sentry/taskworker/registry.py:241 and registry.py:67. Trace how sentry.tasks.send_ping is imported and registered, then make the test reliable so the task is available when its schedule parameters are checked.
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
- 45/100