No online nodes assigned to build on ci.eclipse.org/openmq
Summary
Just like in the case #106 (closed)
Similar happened today, with the last unsuccessful agent to be
(after many attempts to launch others) - some success for a job or two.
And now - next one
and
https://status.eclipsestatus.io/ is green ATM
Steps to reproduce
Go to https://ci.eclipse.org/openmq/ and observe how no job is consumed from queue.
What is the current bug behavior?
Executors are being unsuccessfully launched.
What is the expected correct behavior?
Up to 2 executors started and consuming from the queue.
Relevant logs and/or screenshots
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
Priority
- Urgent
- High
- Medium
- Low
Severity
- Blocker
- Major
- Normal
- Low
Impact
OpenMQ CI unusable.
Activity
Also similar: #781 (comment 473816)
added IT-priorityhigh IT-severitymajor service:jenkins statewip team:releng labels
assigned to @pstankie
I restarted jenkins master.
Also, just a reminder there's limit on how many concurrent jobs can run in parallel, which depends on resource packs available:
https://wiki.eclipse.org/Jenkins#About_resource_packs_and_quotas
I restarted jenkins master.
Thanks!
Also, just a reminder there's limit on how many concurrent jobs can run in parallel, which depends on resource packs available:
https://wiki.eclipse.org/Jenkins#About_resource_packs_and_quotas
Sure, I'm aware. That's why I wrote:
What is the expected correct behavior?
Up to 2 executors started and consuming from the queue.
(knowing the jobs do not combine resources that could cause reduction).
removed statewip label
