What's good fam. I'm trying to debug a weird performance issue in a gradle project. Here is the scan I'll be referring to: https://scans.gradle.com/s/gfqck3xlctvns/tests/overview The scan shows a test run of a single junit test class. It's important to note that this test class does nothing special, nothing complicated, no delays, no sleeps, no synchronizations, etc - just mocking a few objects and verifying correct usage. The first run of this test class is always slow, on the order of seconds, and the others in the class perform to my expectations, in the order of a few milliseconds. Anything off the top of our heads I should look into to debug first? I've tried increasing memory/heapsize, enabling parallel execution with

maxParallelForks

(from Gradle's docs), setting

forkEvery

to both

0

and

1

, using different JDK versions (

11

and

17

), but no smoking gun yet.

how are you mocking? do you happen to use mockito and its

MockitoExtension

?

Forgot to check the mock extension - yeah we have a

resources/mockito-extensions/org.mockito.plugins.MockMaker

file with

mock-maker-inline

. Should probably just be using

mockito-inline

I suppose?

In general I'd advise to stay away from the annotation-based mocking when using mockito. It requires a full classpath scan, which can have significant impact on init times.

This test and others are using

mock<ClassThing>

not the

@Mock

annotation so doesn't look like that issue applies here, although I appreciate the link