Quantcast

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
teetoivo created JENKINS-12994:
----------------------------------

             Summary: 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org

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

mwebber commented on JENKINS-12994:
-----------------------------------

I'm seeing this, or something like it, as well.

I have also recently installed the "Throttle Concurrent Builds Plugin" and the "Exclusion-Plugin", so initially I though it might be related to that, but this ticket suggests it's a core problem.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Dirk Kuypers commented on JENKINS-12994:
----------------------------------------

I am seeing this, too, since 1.452 I think. Maybe this is a hint (or just coincidence?): I never had to kill the pending jobs, I went into "Configure Jenkins->Configure System" and just pressed back, without changing/saving anything. After that the queues got filled again. Maybe others could try this, too, to confirm if this helps.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Sami Tikka commented on JENKINS-12994:
--------------------------------------

I upgraded from 1.451 to 1.453 and all my builds started staying in the queue forever. Exactly same symptom: Build says it is waiting for available executor even though all slaves were online with free executors. Restarting Jenkins did not help. Downgraded back to 1.451 and the problem went away.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Vincent Latombe commented on JENKINS-12994:
-------------------------------------------

I've digged in the history between 1.451 and 1.452, and it seems the issue is coming from the following commit : https://github.com/jenkinsci/jenkins/commit/1ac4872ecdc500c63c0dbfce5e4beb5ce78369e5

You can see at line 920-921 that the method returns if the first element of the waiting list is not ready to build, so it doesn't consider other elements in the waiting list.
waitingList is a TreeSet<WaitingItem> and it looks like it is not properly sorted by timestamp, meaning that the compareTo method is not properly implemented.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Vincent Latombe edited comment on JENKINS-12994 at 3/9/12 11:24 PM:
--------------------------------------------------------------------

I've dug in the history between 1.451 and 1.452, and it seems the issue is coming from the following commit : https://github.com/jenkinsci/jenkins/commit/1ac4872ecdc500c63c0dbfce5e4beb5ce78369e5

You can see at line 920-921 that the method returns if the first element of the waiting list is not ready to build, so it doesn't consider other elements in the waiting list.
waitingList is a TreeSet<WaitingItem> and it looks like it is not properly sorted by timestamp, meaning that the compareTo method is not properly implemented.
               
      was (Author: vlatombe):
    I've digged in the history between 1.451 and 1.452, and it seems the issue is coming from the following commit : https://github.com/jenkinsci/jenkins/commit/1ac4872ecdc500c63c0dbfce5e4beb5ce78369e5

You can see at line 920-921 that the method returns if the first element of the waiting list is not ready to build, so it doesn't consider other elements in the waiting list.
waitingList is a TreeSet<WaitingItem> and it looks like it is not properly sorted by timestamp, meaning that the compareTo method is not properly implemented.
                 

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Chris Nogradi commented on JENKINS-12994:
-----------------------------------------

I tried upgrading to 1.452 and 1.455 and both behave as described above with all jobs remaining in 'Waiting for next executor' state with all nodes free.  Downgrading to 1.451 restores functionality.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

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

To work around this, I have removed the quiet period from all of my jobs (running on 1.455 now). This will mean we will get out of order builds sometimes as it will not necessarily see changes from dependent repos - but we can live with that for a bit until this is fixed.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Daniel Tkatch commented on JENKINS-12994:
-----------------------------------------

I might have the same problem I described here: http://groups.google.com/group/jenkinsci-users/browse_thread/thread/df72335ffe030639
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

wbauer commented on JENKINS-12994:
----------------------------------

I am seeing the same issue with "Waiting for next available executor" when several machines are actually completely free. Issues happens since 1.452.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

DevTools Active commented on JENKINS-12994:
-------------------------------------------

This started for us with our upgrade to 1.455 and continues with 1.456
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Shawn Garner commented on JENKINS-12994:
----------------------------------------

I've noted this issue on 1.452.  
We have job a with a quiet period and three idle executors.
Then job b comes with no wait period.
Job b waits until job a is done.
I've also noticed that job b even when it is on the front of the queue that it seems to wait even though all three executors are free.
It's almost as if it thinks job b has a quiet period too.
They eventually all go through but just not quite the throughput you'd expect with three idle executors.
I've noticed as many as 4 or 5 jobs backed up with all three executors idle.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Krzysztof Malinowski commented on JENKINS-12994:
------------------------------------------------

Same issue here. All builds are blocked until all quiet periods end. This is a serious disadvantage and I would like to vote for fixing this in the first place.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Waldek M commented on JENKINS-12994:
------------------------------------

Same here. In case of many scheduled builds, this may cause them never to happen.
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

mwebber updated JENKINS-12994:
------------------------------

    Priority: Critical  (was: Major)

Bumping priority from Major to Critical, as this problem is adversely affecting a lot of people.
               

> 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
>            Priority: Critical
>
> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

SCM/JIRA link daemon commented on JENKINS-12994:
------------------------------------------------

Code changed in jenkins
User: Andrew Bayer
Path:
 changelog.html
 core/src/main/java/hudson/model/Queue.java
http://jenkins-ci.org/commit/jenkins/e4abef20fbdb71971085e7507d7fff4b92676368
Log:
  Merge pull request #419 from Vlatombe/jenkins-12994

[FIX JENKINS-12994] Quiet period is blocking other jobs in queue





               

> 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
>            Priority: Critical
>
> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

dogfood commented on JENKINS-12994:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1623|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1623/]
     [FIX JENKINS-12994] Quiet period is blocking other jobs in queue (Revision 394e9d6c0488fae6834d97a158a018abb31f3179)
Update changelog for JENKINS-12994 (Revision 07b3f2cccb077df85617f2748f9b329528bc263b)

     Result = SUCCESS
Vincent Latombe : [394e9d6c0488fae6834d97a158a018abb31f3179|https://github.com/jenkinsci/jenkins/commit/394e9d6c0488fae6834d97a158a018abb31f3179]
Files :
* core/src/main/java/hudson/model/Queue.java

Vincent Latombe : [07b3f2cccb077df85617f2748f9b329528bc263b|https://github.com/jenkinsci/jenkins/commit/07b3f2cccb077df85617f2748f9b329528bc263b]
Files :
* changelog.html

               

> 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
>            Priority: Critical
>
> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

OHTAKE Tomohiro resolved JENKINS-12994.
---------------------------------------

    Resolution: Fixed
   

> 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
>            Priority: Critical
>
> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

SCM/JIRA link daemon commented on JENKINS-12994:
------------------------------------------------

Code changed in jenkins
User: Vincent Latombe
Path:
 core/src/main/java/hudson/model/Queue.java
http://jenkins-ci.org/commit/jenkins/394e9d6c0488fae6834d97a158a018abb31f3179
Log:
  [FIX JENKINS-12994] Quiet period is blocking other jobs in queue
Queue#maintain() was returning too soon



               

> 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
>            Priority: Critical
>
> 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

       
12
Loading...