[JIRA] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates We decided on making 1.625 the next LTS baseline. Change By: Daniel Beck Labels: deadlock lts-candidate queue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Change By: Daniel Beck Labels: deadlocklts-candidate queue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Change By: Daniel Beck Labels: deadlocklts-candidate queue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Change By: Oleg Nenashev Labels: deadlock lts-candidate queue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Oleg Nenashev commented on JENKINS-30080 Re: Possible deadlock between scheduleBuild() and NodeProvisioner updates https://github.com/jenkinsci/jenkins/pull/1785 has been merged into 1.625 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Change By: Oleg Nenashev Environment: jenkins-1.607+ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates Issue Type: Bug Assignee: Unassigned Components: core Created: 21/Aug/15 9:48 AM Labels: deadlock queue Priority: Critical Reporter: Oleg Nenashev JIRA was down when I've created the issue NodeProvisioner#getPendingLaunches() and NodeProvisioner#update() may get deadlocked if somebody retrieves a list of pending launches in the build scheduler. It also applies to all other methods guarded by provisioningLock, because NodeProvisioner#update() locks the queue after locking provisioningLock. Pull requests: https://github.com/jenkinsci/jenkins/pull/1777 (queue-locking implementation, declined) https://github.com/jenkinsci/jenkins/pull/1785 (lock-free implementation, accepted)
