[GRADLE-3205] Parallel execution is horribly broken after upgrading to 2.0+. Created: 26/Nov/14  Updated: 02/Feb/17  Resolved: 02/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Pepper Lebeck-Jobe
Resolution: Duplicate Votes: 1

Issue Links:
Related
Related to GRADLE-2788 parallel build may download the same ... Resolved
Related to GRADLE-3309 Excessive downloads during resolution Resolved

 Description   

We have been using parallel execution since it was added, but after upgrading to 2.0 we have been getting various non deterministic bugs, especially around dependency downloading.

After upgrading to 2.1 or the 2.2 release candidate this has gotten even worse, and we get many messages saying metadata is corrupt in snapshots, and our build is never able to finish correctly, often we have to delete the gradle cache entirely, as the downloaded dependencies are completely broken.

Sometimes we also have to delete the local .gradle directory in the project, as that too can become corrupt, beyond what clean will fix.

 Comments   
Comment by Gradle Forums [ 26/Nov/14 ]

Hi Mathias,

Unfortunately I'm not sure what we can do with this report. Any extra info you can provide such as stack traces or error messages would be helpful.

Comment by Gradle Forums [ 26/Nov/14 ]

Well I can see it wasn't the most usefull bug-report. I think I got carried away by my frustration .

We just got a failure during a parallel build using Gradle 2.1 on windows 7

[1]https://gist.github.com/mathiasbn/78c...

I will post other stacktraces if I get them
----------------------------------------------------------------------------------------
[1] https://gist.github.com/mathiasbn/78c4a2fc302e36886305

Comment by Gradle Forums [ 26/Nov/14 ]

Gist updated.

Comment by Paul Merlin [ 06/Sep/16 ]

Isn't this a duplicate of GRADLE-3206?

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 [ 02/Feb/17 ]

I believe this issue is a duplicate.

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