[JIRA] (JENKINS-6565) Hudson stuck on inexistent job

2016-07-13 Thread stephenconno...@java.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 stephenconnolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-6565  
 
 
  Hudson stuck on inexistent job   
 

  
 
 
 
 

 
Change By: 
 stephenconnolly  
 
 
Assignee: 
 stephenconnolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-6565) Hudson stuck on inexistent job

2012-05-17 Thread klei...@gmail.com (JIRA) 

[ 
https://issues.jenkins-ci.org/browse/JENKINS-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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