Abacn commented on PR #26775: URL: https://github.com/apache/beam/pull/26775#issuecomment-1553718783
Enable the build cache by a single line does not work (commit: https://github.com/apache/beam/pull/26775/commits/2aaf6c72a200ffed912188bb57a92eaee29e3f62): ``` 17:57:17 * What went wrong: 17:57:17 Timeout waiting to lock daemon addresses registry. It is currently in use by another Gradle instance. 17:57:17 Owner PID: unknown 17:57:17 Our PID: 960477 17:57:17 Owner Operation: unknown 17:57:17 Our operation: 17:57:17 Lock file: /home/jenkins/.gradle/daemon/7.5.1/registry.bin.lock 17:57:17 17:57:17 * Try: 17:57:17 > Run with --info or --debug option to get more log output. 17:57:17 > Run with --scan to get full insights. 17:57:17 17:57:17 * Exception is: 17:57:17 org.gradle.cache.LockTimeoutException: Timeout waiting to lock daemon addresses registry. It is currently in use by another Gradle instance. 17:57:17 Owner PID: unknown 17:57:17 Our PID: 960477 17:57:17 Owner Operation: unknown 17:57:17 Our operation: 17:57:17 Lock file: /home/jenkins/.gradle/daemon/7.5.1/registry.bin.lock 17:57:17 at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.timeoutException(DefaultFileLockManager.java:344) ``` @clayburn I would understand that the gradle enterprise plugin is not compatible with local build cache anymore? In this case, I would suggest roll out the change of #26351 until the remote build cache is also available. Currently it is causing regression on our (already flaky) infra. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
