[
https://issues.jenkins-ci.org/browse/JENKINS-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163252#comment-163252
]
cpringle commented on JENKINS-7667:
-----------------------------------
I've just installed this plugin onto Jenkins and am getting the same behaviour
as described in the initial bug report. I have 6 executors, but only 2 are
available during the day. I currently have executors 2 and 6 free (the rest are
reserved), and there are 2 jobs stuck in the build queue even though there are
2 spare executors.
Are we able to get a fix for this?
> Build waits for next available executor even if several are available
> ---------------------------------------------------------------------
>
> Key: JENKINS-7667
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7667
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: Hudson 1.379, slave-squatter 1.1, heavy-job 1.0
> Reporter: torbent
> Assignee: Kohsuke Kawaguchi
> Attachments: load-predictor.patch
>
>
> (Couldn't find slave-squatter nor heavy-job as components, so posted in core)
> I think there's a problem in the cooperation between these components.
> I started using them yesterday to replace a more complicated mix of
> "heavy-slaves".
> I have one slave with 8 executors. I configured it, using slave-squatter, to
> reserve 3 of these during office hours, leaving 5 for use. I then noticed a
> job with weight 3 claiming to wait for next available executor even though it
> was the only job in the queue and there were no builds on the slave (or
> anywhere, actually).
> I tried lowering the reservation of the slave to 2 (i.e. 6 executors free)
> which caused the build to start - but having to keep an eye on these
> situations is not why I run Hudson ;-)
> The only issue I could find that smells a bit like this was JENKINS-7033 (Job
> in build queue is not executed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
