[ 
https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160040#comment-160040
 ] 

allenservedio commented on JENKINS-12994:
-----------------------------------------

I am seeing the same thing in 1.454. Even worse, I am starting to see deadlocks 
around this. I had to go in and kill a three jobs where two of them were stuck 
in an infinite loop of quiet periods and the third (a scheduled job) was stuck 
waiting for an executor. As I was not watching the builds, they were stuck in 
that state for over an hour before I caught them (the quiet period for the 
other two jobs was 190 seconds, it just kept cycling through quiet periods). 
                
> Quiet period is blocking other jobs in queue
> --------------------------------------------
>
>                 Key: JENKINS-12994
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12994
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: teetoivo
>
> Starting from version 1.452, a job in queue waiting for the quiet period to 
> pass is blocking all other jobs that have been queued after it.
> Example:
> # Job A has quiet period set to 10 seconds
> # Job B has quiet period set to 300 seconds
> # Job C has quiet period set to 100 seconds
> # Jobs get queued in A-B-C order.
> # Job A starts executing after 10 seconds
> # After 100 seconds, status of job C changes to "pending - Waiting for next 
> available executor" even if free executors are available
> # After 300 seconds both jobs B and C start executing
> This problem is hardly visible when short quiet periods are used but becomes 
> problematic with longer quiet periods or plugins like Naginator that will 
> increase the quiet period to hours if the builds fail enough.
> Version 1.451 is the last release where this problem isn't visible. From 
> public releases, at least 1.452 and 1.454 are affected.

--
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

        

Reply via email to