Apply plugin com.gradle.build-scan takes up to 5 seconds


(David Lee) #1

I enabled the Build Scan plugin in my Android project and noticed an additional delay during the configuration phase. With --debug enabled I can see there is a delay of about 5 seconds after the line
"Build operation ‘Apply plugin com.gradle.build-scan to root project ‘android’’ started"

here is a snippet of the log with timestamps:
13:59:52.026 [DEBUG] [org.gradle.internal.progress.DefaultBuildOperationExecutor] Build operation ‘Apply plugin com.gradle.build-scan to root project ‘android’’ started
13:59:57.036 [DEBUG] [org.gradle.model.internal.registry.DefaultModelRegistry] Project : - Registering model element ‘tasks.buildScanPublishPrevious’ (hidden = false)
13:59:57.037 [null] [org.gradle.cache.internal.DefaultFileLockManager]
13:59:57.037 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
13:59:57.037 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.

and here is a build scan:
https://gradle.com/s/ixkrcnzbyaita

Is this additional delay experienced by others or is there perhaps something wrong with my project setup? I’m happy to provide more details as needed


(Stefan Oehme) #2

You’re probably being hit by this terrible regression in MacOs Sierra that still hasn’t been fixed: https://thoeni.io/post/macos-sierra-java/


(David Lee) #3

Yes that fix solved the issue good catch!