[GRADLE-2162] When getting a 'CorruptedCacheException' Gradle should do its best to repair or at least delete the corrupted cache Created: 08/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Some of my Gradle STS tooling tests have started failing because of exceptions like these:

Caused by: org.gradle.cache.btree.CorruptedCacheException: Corrupted IndexBlock 31183747 found in cache '/home/bamboo/.gradle/caches/1.0-milestone-3/fileSnapshots/cache.bin'.
at org.gradle.cache.btree.FileBackedBlockStore$BlockImpl.blockCorruptedException(FileBackedBlockStore.java:239)
at org.gradle.cache.btree.FileBackedBlockStore$BlockImpl.read(FileBackedBlockStore.java:215)
at org.gradle.cache.btree.FileBackedBlockStore.read(FileBackedBlockStore.java:91)
at org.gradle.cache.btree.CachingBlockStore.read(CachingBlockStore.java:84)
at org.gradle.cache.btree.FreeListBlockStore.read(FreeListBlockStore.java:78)
at org.gradle.cache.btree.StateCheckBlockStore.read(StateCheckBlockStore.java:61)
at org.gradle.cache.btree.BTreePersistentIndexedCache.load(BTreePersistentIndexedCache.java:169)
at org.gradle.cache.btree.BTreePersistentIndexedCache.access$1300(BTreePersistentIndexedCache.java:40)
at org.gradle.cache.btree.BTreePersistentIndexedCache$IndexBlock.find(BTreePersistentIndexedCache.java:465)
at org.gradle.cache.btree.BTreePersistentIndexedCache$IndexBlock.access$700(BTreePersistentIndexedCache.java:338)
at org.gradle.cache.btree.BTreePersistentIndexedCache.put(BTreePersistentIndexedCache.java:133)
... 41 more

When the cache is corrupt... it would be nice if Gradle tries at least to delete the corrupted cache. As it stands now all builds keep failing repeatedly unless the user manually deletes the Gradle cache.

This isn't necessaryly an easy thing to do if the cache is located on a CI build server to which the user doesn't have direct ssh/login access.
Rather than leave corrupted caches around, Gradle should at least attempt to delete them so that on a successive build the problem will hopefully not still be there.

Kris

 Comments   
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:14:23 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.