[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

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


We have the following setup:

project A
task1 of type GradleBuild, executing (project B task sometask)
task2 of type GradleBuild, executing (project B task sometask)

project B
task sometask

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]([1]https://gist.github.com/mathiasbn/a45...)
[1] https://gist.github.com/mathiasbn/a4584d28692f09723291

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:44:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.