|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Also looks like this deadlock would only happen if the job were marked as being capable of concurrent builds. Not clear to me whether it requires the presence of CLH; looks like it might be possible (if less likely) without it.
Note that the behavior of LogRotator for concurrent-capable jobs is not well defined: it might wind up deleting the wrong number of builds, since it does not hold a lock on a Run for the duration of its loop, but just does a one-off calculation of old build candidates. Probably harmless normally.