You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using 2 dependent workflows and the autoscaler with WOODPECKER_MIN_AGENTS=0 and WOODPECKER_AGENT_IDLE_TIMEOUT=0s it is possible to create the above queue state.
The task is waiting for dependencies, but all dependencies are already done.
The task is moved to pending when an agent is manually added. It should move to pending without an agent being present.
Because there is no task in pending the autoscaler also doesn't create a new agent, which creates a deadlock.
Steps to reproduce
Create two dependent workflows.
Use the autoscaler with WOODPECKER_MIN_AGENTS=0 and WOODPECKER_AGENT_IDLE_TIMEOUT=0s
Expected behavior
When a task has no dependencies left it should move from waiting for dependencies to pending.
Component
server
Describe the bug
Using 2 dependent workflows and the autoscaler with
WOODPECKER_MIN_AGENTS=0
andWOODPECKER_AGENT_IDLE_TIMEOUT=0s
it is possible to create the above queue state.The task is waiting for dependencies, but all dependencies are already done.
The task is moved to pending when an agent is manually added. It should move to pending without an agent being present.
Because there is no task in pending the autoscaler also doesn't create a new agent, which creates a deadlock.
Steps to reproduce
WOODPECKER_MIN_AGENTS=0
andWOODPECKER_AGENT_IDLE_TIMEOUT=0s
Expected behavior
When a task has no dependencies left it should move from
waiting for dependencies
topending
.System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: