[GRADLE-3283] Finalizer tasks can take a very long time Created: 16/Apr/15 Updated: 27/Jan/17 Resolved: 24/Jan/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | 2.10-rc-1 |
Type: | Bug | ||
Reporter: | Sterling Greene | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Description |
Hi. Would it be possible to take a look at the performance of DefaultTaskExecutionPlan.enforceFinalizerTasks()? If a finalizer task has dependencies of its own, this call can take a very long time. Sample script to reproduce: defaultTasks "actualTask" 50.times { index -> } task finalizerTask task actualTask Thank you for your help! |
Comments |
Comment by Sterling Greene [ 16/Apr/15 ] |
https://discuss.gradle.org/t/finalizer-tasks-can-take-a-very-long-time/9145 |
Comment by Daz DeBoer [ 18/Sep/15 ] |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 24/Jan/17 ] |
The pull request has been merged. I am assuming it's fixed. |