[GRADLE-3253] multiple GradleBuild-typed tasks combined with parallel execution leads to concurrency errors in referred project Created: 02/Mar/15 Updated: 10/Feb/17 Resolved: 10/Feb/17
We have the following setup:
Now, if we execute a task on project A that depends on both task1 and task2, they are run concurrently, but then it seems they inadvertently call "sometask" concurrently on project B as well, leading to various concurrency errors there, some of the errors we have seen:
[Gist of stacktrace](https://gist.github.com/mathiasbn/a45...)
|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 [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.