[JIRA] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi, Just updated the jazz work item with the full threadDump as reported from Jenkins at the time of another personal build hanging. Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, The build had failed before that. The load step had passed and it was a legitimate failure during the build. I'll try and grab all thread data next time . Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, Had another hanging build today. Here is the Jenkins console output: Started by user anonymous Building on master in workspace /ccbdata/build/TRUNKP RTC : checkout... RTC : Build initiated by request from RTC RTC Checkout : Source control setup RTC Checkout : Fetching files to fetch destination "/ccbdata/build/TRUNKP/src" ... It got stuck there and just had the loading symbol. Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James Can you look at the RTC Build result for this build that was started in RTC. When you open the build result there are tabs of different pieces of info. Is there an Activities tab? Does the Activities tab have any entries. Specifically I am interested in one that says "Fetching files" and whether it was complete or not. Can you tell if the source code was all loaded or not? Was the stack trace showing it was stuck in the same place again? Were there other threads (or the other executor) running and were any of them running RTC or Plugin code? Did the build prior to this one finish normally or was it cancelled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source I have raised : 336647: Personal builds can encounter deadlock when fetching source for this in jazz.net This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, I've attached a screenshot of the activities tab for the build result as viewed in RTC to the jazz.net work item that you posted. I unfortunately can't tell if all the source code was loaded as subsequent personal builds have been done which have re-used the workspace. The thread dump is no longer available for that build, however I did look at it and it was waiting for a lock at the same place. I can't say for this build in particular but generally, we have 2 executors running and they will both be RTC builds. Therefore it is likely that there was another build running at the same time that would have checked out source from RTC etc. The previous personal build before that had failed for a legitimate reason. If you're talking about a build for any job that was running at the same time as the one that hanged, I'm not sure what build that was as the timing info for the hanging build has been lost after killing the Jenkins process. Thanks, James This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James, I think the thread dump (of all the threads) would help (for next time). By previous build, I mean the Jenkins build for the same job that just ran previous to it. For example it looks like TRUNKP was the job that was run with the personal build workspace. If that was build #73 then how did the TRUNKP build #72 end? Legitimate failure (test failure as opposed to not a failure during the load step, not cancelled). Just trying to exclude the idea of a previous build impacting the next one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.