|
||||||||
|
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.
Jesse Glick: I'm not so sure. It really looks like the issue in Tim Wood's last comment is the same JENKINS-24519: When Jenkins is quieting down, FlyWeight tasks aren't scheduled, and use a real executor once they are.
The change you link to, and the one I link to in JENKINS-24519 are essentially the same code.
Note that IMO it makes sense to not schedule Flyweight tasks while quieting down if they're not NonBlockingTask, however it makes no sense for them to be treated like normal ("heavyweight") tasks afterwards.