[
https://issues.jenkins-ci.org/browse/JENKINS-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160980#comment-160980
]
wbauer commented on JENKINS-9688:
---------------------------------
I see the same issue sporadically (Jenkins 1.454 currently).
The build seems to be stuck in the assignment phase and no thread or sockets
refers to it at all.
The build is not visible in any queue or listing except on the job itself.
The build shows:
"Started 2 hr 1 min ago
Build is being executed for null on master"
.
This build is not killable meaning that I have to restart the master to get rid
of the build...
> Build runs on master without executor and get stuck
> ---------------------------------------------------
>
> Key: JENKINS-9688
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9688
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: protocol7b
>
> In the ASF Jenkins, we do not allow builds to run on master. Thus, we have
> set the number of executors on master to zero. Even so, one build recently
> (https://builds.apache.org/hudson/job/Axis2/774/) got assigned to run on
> master. The build is configured with a label to run on one of the slaves, but
> somehow Jenkins assigned it incorrectly.
> Running on master also meant it got stuck, presumably due to the lack of
> executors, without any way of stopping it.
--
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
