Anyone had issues before with a `ClassNotFound: Gr...

# gradle

[Sam Pengilly]

Anyone had issues before with a ClassNotFound: GradleWorkerMain error in gradle builds? (Note that’s GradleWorkerMain, not GradleWrapperMain which is more commonly discussed as a source of issues).
This is happening only on CI build machines, and seemingly only upon reaching a test task (assemble ran fine, detekt ran fine, tests fail with that error).
In my CI environment there’s a collection of different projects with different gradle versions and the build machine has a few versions of JDK installed, so I feel like there’s potential for clashes/corruption somehow creeping in, especially since deleting the gradle caches seems to make the problem go away for a little while. Not really sure where to start to diagnose what exactly is triggering it

I’ve found next to no info on it in searches, everything just directs to the aforementions “GradleWrapperMain” error

[Sam Pengilly]

> Task :app:testDebugUnitTest FAILED
Error: Could not find or load main class worker.org.gradle.process.internal.worker.GradleWorkerMain
Caused by: java.lang.ClassNotFoundException: worker.org.gradle.process.internal.worker.GradleWorkerMain

[Sam Pengilly]

The gradle wrapper is being used as well

[xenomachina]

Hello. Did you ever resolve this issue? We're running into something that sounds a lot like this: https://gradle-community.slack.com/archives/CAHSN3LDN/p1737580256115419

[Sam Pengilly]

We ended up moving to a different CI environment with more isolated build agents and haven't seen it happen again

[xenomachina]

Thanks for your reply! We came up with what seems to be a fix: instead of deleting old stuff from the cache, we just erase the entire cache when it gets too big. I think Gradle can't deal with parts of its cache getting deleted, but this does mean that we periodically have a completely empty cache.