-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Closed as duplicate of#8375
Labels
a:bugclosed:duplicateDuplicated or superseeded by another issueDuplicated or superseeded by another issuein:daemonin:file-locking
Description
Running parallel gradle builds on Jenkins causes "Timeout waiting to lock journal cache" every now and then.
Notes:
We have not seen this behavior before switching to Gradle 5.
Disabling the Gradle daemon will not mitigate the issue.
Expected Behavior
When running gradle builds in parallel, no lock timeout should occur.
Current Behavior
Caused by: org.gradle.cache.LockTimeoutException: Timeout waiting to lock journal cache (/srv/jenkins/.gradle/caches/journal-1). It is currently in use by another Gradle instance.
Owner PID: 31422
Our PID: 3410
Owner Operation:
Our operation:
Lock file: /srv/jenkins/.gradle/caches/journal-1/journal-1.lock
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.lock(DefaultFileLockManager.java:291)
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.<init>(DefaultFileLockManager.java:161)
at org.gradle.cache.internal.DefaultFileLockManager.lock(DefaultFileLockManager.java:107)
at org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess.incrementLockCount(LockOnDemandCrossProcessCacheAccess.java:106)
at org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess.acquireFileLock(LockOnDemandCrossProcessCacheAccess.java:168)
at org.gradle.cache.internal.CrossProcessSynchronizingCache.put(CrossProcessSynchronizingCache.java:63)
at org.gradle.api.internal.changedetection.state.DefaultFileAccessTimeJournal.setLastAccessTime(DefaultFileAccessTimeJournal.java:89)
at org.gradle.internal.resource.local.SingleDepthFileAccessTracker.markAccessed(SingleDepthFileAccessTracker.java:60)
at org.gradle.internal.resource.local.SingleDepthFileAccessTracker.markAccessed(SingleDepthFileAccessTracker.java:48)
at org.gradle.internal.resource.cached.AbstractCachedIndex.lookup(AbstractCachedIndex.java:74)
at org.gradle.api.internal.artifacts.ivyservice.modulecache.artifacts.DefaultModuleArtifactCache.lookup(DefaultModuleArtifactCache.java:77)
at org.gradle.api.internal.artifacts.ivyservice.modulecache.artifacts.InMemoryModuleArtifactCache.lookup(InMemoryModuleArtifactCache.java:63)
at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository$LocateInCacheRepositoryAccess.resolveArtifactFromCache(CachingModuleComponentRepository.java:323)
at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository$LocateInCacheRepositoryAccess.resolveArtifact(CachingModuleComponentRepository.java:290)
at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.lambda$resolveArtifact$12(ErrorHandlingModuleComponentRepository.java:186)
at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.tryResolveAndMaybeBlacklist(ErrorHandlingModuleComponentRepository.java:242)
... 245 more
Context
- Using gradle wrapper
- gradle version 5.2.1
Steps to Reproduce (for bugs)
Run builds in parallel on the same machine.
KrzysztofKowalczyk, lkc0987, TanyaDolgopolova, Kipre, sedovalx and 71 more
Metadata
Metadata
Assignees
Labels
a:bugclosed:duplicateDuplicated or superseeded by another issueDuplicated or superseeded by another issuein:daemonin:file-locking