galaxyproject / galaxyproject/pulsar
Resilience Suite flakiness at fixture startup
- Dominant language
- Python
- Stars
- 46
- Forks
- 62
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 15
Description
The Resilience Suite job in the pulsar workflow intermittently fails at fixture setup with:
```
TimeoutError: Pulsar did not bind consumers within 60.0s
test/resilience/harness/pulsar_control.py:199
```
The bind-wait helper in `harness/pulsar_control.py` documents this path as racy: "Polling the broker for a non-zero consumer count is racy after a kill+restart cycle: the old consumer count can linger." The 60s wait at pulsar_control.py:199 is the hard cutoff that trips.
Contributor guide
Research direction
Start in test/resilience/harness/pulsar_control.py at the bind-wait helper and the 60-second cutoff on line 199. Run the Pulsar workflow's Resilience Suite to reproduce the fixture-startup failure, then verify that the bind step completes reliably after a kill-and-restart cycle without the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100