I am using gradle project for building Selenium Automation testing framework.
To trigger the execution i am using command prompt and running gradlew clean and gradlew test commands.
Now while using gradlew clean, its running for hours and i ends up with terminating the execution.
and after restarting the system it is again working as expected for 2 or 3 executions but and I am facing the same issue again and again.
what could be the reason and how I can fix this issue?
Never heard of such behavior, so it is hard to guess what causes this in your case.
If you can knit an MCVE that reproduces the problem also on other computer, you might report a bug.
Otherwise you probably have to debug - or at least use --debug as a first step - to see what is happening.
Don’t get fooled though by the regular daemon registry lock related messages you will see, they are just normal maintenance work while the build is running.