Hey @zzak,
For my case I posted the problem and the solution in here:
Basically jest is not detecting the number of cpus of the container but from underlying machine. This makes it create lots of threads.
I imagine something similar is happening for the case described here.
1 Like