title: Could not create service of type FileHasher using GradleUserHomeScopeServices.createCachingFileHasher()
body: <h1>Here is the context of my problem:</h1>
  
  <ul>
  <li>a gitlab ci yml pipeline </li>
  <li>several jobs in the same internship</li>
  <li>all jobs use a task gradle requiring the use of his cache</li>
  <li>all jobs share the same gradle cache </li>
  </ul>
  
  <h1>My problem:</h1>
  
  <p>sometimes, when there are several pipelines at the same time, I get :</p>
  
  <p>What went wrong:
  Could not create service of type FileHasher using GradleUserHomeScopeServices.createCachingFileHasher().</p>
  
  <blockquote>
    <p>Timeout waiting to lock file hash cache (/cache/.gradle/caches/5.1/fileHashes). It is currently in use by another Gradle instance.
      Owner PID: 149
      Our PID: 137
      Owner Operation: 
      Our operation: 
      Lock file: /cache/myshop/reunion/.gradle/caches/5.1/fileHashes/fileHashes.lock</p>
  </blockquote>
  
  <p>I can't find any documentation about the lock system used by gradle. I don't understand why locks are positioned when the gradle action doesn't write to cache dir.</p>
  
  <p>Does anyone know how locks work? Or can I simply change the duration of the timeout to allow concomitant tasks to wait their turn long enough before failing?</p>
  
  <p>Translated with www.DeepL.com/Translator</p>
  
  <p>I tried to tun gradle without a daemon, did not work.</p>