Any idea as to why when we run gradle deploy - initializing takes 60 or more seconds. Once initializing is complete a couple of seconds later the deploy is complete.
On the first call, gradle has to start up a daemon (background thread). This daemon will run in the background and can be reused by subsequent calls. Depending on the hardware of your computer and other tasks running, this can take anywhere from a few seconds to a minute or more on slower devices. It’s normal and nothing to worry about.
1 Like
I agree that the first time should take sometime, but my problem is that my PC sits in the “Initializing” state for over 60 before it starts to do anything 95% of time I try and deploy or build. I have reinstalled the NI and WPI software.
It happens over 95% of the time when I try and deploy code.
Is it only deploy that has the delay or do other gradle tasks like build also have the delay?
Deploy, build and clean all seem to have the problem. I have not tried other gradlew commands.
Yesterday when I reinstalled ni and wpi. I had less than one second initializing times for about 3 times. Then it want back to initializing times over 60 seconds.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.