[
https://issues.jenkins-ci.org/browse/JENKINS-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162901#comment-162901
]
Kyle Leinen commented on JENKINS-6565:
--------------------------------------
I am also seeing this. The job cannot be cleared/cancelled without restarting
Jenkins completely, which is a pain.
> Hudson stuck on inexistent job
> ------------------------------
>
> Key: JENKINS-6565
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6565
> Project: Jenkins
> Issue Type: Bug
> Components: locks-and-latches
> Reporter: rombert
> Assignee: stephenconnolly
> Priority: Blocker
> Attachments: hudon-stuck-system-information.txt,
> hudson-stuck-enabled-plugins.txt, hudson-stuck-executors.png,
> hudson-stuck-home-page-queue.png, hudson-stuck-thread-dump.txt
>
>
> After a couple of days, Hudson seems to see a a 'phantom' build queued ,
> which does not execute at all, but it blocks the next job from running. The
> currently executing build is 'Collectors' and the stuck build is
> 'SportsEngine-Collection' . The stuck build is a Maven2 build, using the
> locks-and-latches plugin, polling SVN every minute.
--
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
