[GRADLE-2905] Build fails with: "Corrupted IndexBlock 619" Created: 30/Sep/13  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: 0


Testing out Gradle (and Groovy). When I do a "gradle clean build" it fails, encouraging me to submit a report here

Root cause seems to be:
"Caused by: org.gradle.cache.internal.btree.CorruptedCacheException: Corrupted IndexBlock 6198 found in cache '/Users/stoyle/projects/repos/km-groovy-testing/.gradle/1.8/taskArtifacts/outputFileStates.bin'."

All details, gradle build file, groovy test file and build output can be found here:

On MacOSX 10.8.5, Gradle 1.8, Groovy 2.1.7. Testing with IntelliJ 12.1.4.

All I did was to paste some code into the Greet.groovy file, and rename the Greet class to Greet1, since the Groovy compiler complained.

Workaround was to remove the .gradle folder.

[1] https://gist.github.com/stoyle/a3507c90bc2c51b420b5

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:34:37 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.