This message was deleted.

I don't think Gradle does anything to restrict this, so I'd think the test jvms have access to all CPU cores.

I'm definitely seeing Runtime.getRuntime().availableProcessors() return one, and all the thread pools get configured accordingly, so if it's not Gradle I don't know who's doing it

Does Gradle itself has access to more cores?

And since Gradle likes to fork a bunch of jvms to run test, it makes sense that it would want to restrict each jvm to 1 core

I don't think that would make sense and I'd really wonder if Gradle did, especially by default. I'm not even aware of an option to restrict that in Java itself without using some OS feature from outside.

found it. org.gradle.jvmargs=-Xmx1g -XX:TieredStopAtLevel=1 -XX:+UseParallelGC -XX:ActiveProcessorCount=1 \

oh yea that will do it. best to leave that option out, the JVM will detect the available cores in the container/server.

this project sets that in 3 places, wtf

Ah, well, an XX option you set yourself, well yeah, then that explains it. 😄

an XX option from a project with hundreds of other contributors, yes

Didn't mean "you" like "you personally" but like "your project". Sorry if it came across badly. 🙂