[GRADLE-3420] uploadArchives task is not parallel safe Created: 25/Mar/16  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: Bug
Reporter: Pepper Lebeck-Jobe Assignee: Unassigned
Resolution: Duplicate Votes: 0

Attachments: HTML File run737    
Issue Links:
Related to GRADLE-2582 Parallel resolution of artifacts Resolved


When running an older version of MavenMultiProjectPublishIntegrationTest we were testing one invocation of Gradle's uploadArchive task with two subprojects that both tried to upload artifacts to a local maven repo.

This gist shows the stack trace.

Please note, this bug is not easily reproducible. I've run a shell loop 1000 times and not been able to reproduce the problem. I set up this sample project to reproduce the issue. And I actually did get it to fail one time where I forgot the stacktrace flag. But, in a loop of 1000 invocations of gradle clean uploadArchives -s I have not been able to make it happen again. My gradle.properties file looks like this:


Comment by Pepper Lebeck-Jobe [ 25/Mar/16 ]

Ran it another 1000 times, but this time the loop was simply: rm -rf maven-repo; gradle uploadArchives -s this time exactly one of the 1000 operations failed. I'm uploading the log from that build.

Comment by Pepper Lebeck-Jobe [ 25/Mar/16 ]

Failed run of rm -rf maven-repo; gradle uploadArchives -s on the sample project.

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 Pepper Lebeck-Jobe [ 18/Nov/16 ]

I think this is still an issue. I also believe there is enough information in the original bug report to reproduce the failure. It isn't easy, but running a couple thousand iterations will probably cause it to reproduce.

Comment by Eric Wendelin [ 24/Jan/17 ]

This has been moved to https://github.com/gradle/gradle/issues/1237

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