That was it - removing geode-core/dunit and associated junk fixed the
problem. Thanks Dan
Le 3/13/2017 à 3:01 PM, Dan Smith a écrit :
I've seen this happen before (on linux) if you have very large files in
your workspace that rat is trying to analyze. Unfortunately, rat is not
just looking at files tracked by git but any files that are in your
checkout directory and aren't excluded in gradle/rat.gradle.
So maybe check to see if you have any large files lying around in your
checkout?
-Dan
On Mon, Mar 13, 2017 at 2:55 PM, Bruce Schuchardt <bschucha...@pivotal.io>
wrote:
The "rat" task has started hanging on my Windows 7 machine. I've run with
& without the gradle daemon and get the same result. With debug output it
periodically logs this:
14:53:55.907 [DEBUG] [org.gradle.launcher.daemon.server.Daemon]
DaemonExpirationPeriodicCheck running
14:53:55.908 [DEBUG] [org.gradle.launcher.daemon.server.health.DaemonStatus]
GC rate: 0.0/s
14:53:55.911 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager]
Waiting to acquire shared lock on daemon addresses registry.
14:53:55.912 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager]
Lock acquired.
14:53:55.913 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager]
Releasing lock on daemon addresses registry.
