[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
|Reporter:||Kris De Volder||Assignee:||Unassigned|
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'.
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.
|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:
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.