Flaky test: tests/sentry/workflow_engine/test_integration.py::TestWorkflowEngineIntegrationFromErrorPostProcess::test_slow_condition_workflow_with_conditions
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
Failing test: `tests/sentry/workflow_engine/test_integration.py::TestWorkflowEngineIntegrationFromErrorPostProcess::test_slow_condition_workflow_with_conditions`
Sentry sha: 4a8dadc9c184ad93a761561c5f57437a29cd3300
Run: https://github.com/getsentry/sentry/actions/runs/22283662803
```
[1m[31mtests/sentry/workflow_engine/test_integration.py[0m:379: in test_slow_condition_workflow_with_conditions
mock_trigger.assert_called_once()
[1m[31m/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/unittest/mock.py[0m:956: in assert_called_once
raise AssertionError(msg)
[1m[31mE AssertionError: Expected 'apply_async' to have been called once. Called 0 times.[0m
```
Contributor guide
Research direction
Start with tests/sentry/workflow_engine/test_integration.py, especially test_slow_condition_workflow_with_conditions around the failing mock_trigger.assert_called_once() at line 379. Run the named test and inspect the surrounding workflow integration setup to determine why apply_async is called zero times. Done means the test passes reliably with the expected call.
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