[
https://issues.jenkins-ci.org/browse/JENKINS-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160682#comment-160682
]
Mikhail Churikov commented on JENKINS-11548:
--------------------------------------------
Ivan Vovk and I fixed the bug in our local version of Jenkins sources. In the
case FLYWEIGHT_SUPPORT set true, Jenkins trys start second matrix parent
executor on the stage MappingWorkSheet and goes to wait. That activity was
blocked. In the opposite case, we block occupying executors by the matrix
parent in the same way. We also pass HeavyJobProperty to trigered nodes.
How cam we merge this fix with trunk?
May I commit to trunk or carry patch?
> Heavy Job plugin not working with Matrix jobs
> ---------------------------------------------
>
> Key: JENKINS-11548
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11548
> Project: Jenkins
> Issue Type: Bug
> Components: heavy-job, matrix
> Affects Versions: current
> Reporter: Alex Vesely
> Assignee: Mikhail Churikov
> Labels: heavy-job, matrix
>
> If a Matrix job has a 'weight' not equal to 1, it fails to start its children
> and just runs indefinitely. Also, it is shown as 'running' in Job view even
> after cancelling, which is fixed only by restarting Jenkins.
> I think there is a problem with starting FlyWightTask. Jenkins wait for
> thread in "offer.event.block();" (Queue.java::830 .Jenkins code). Executor
> #-1 seems to not release, as it should.
> FreeStyle projects starts normally even it's weight > 1.
--
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
