Closed apaniel closed 1 year ago
Thanks for reporting the problem. We believe your problem is from using the workerIdleMemoryLimit
setting in your jest configuration. This forces jest
to run your tests in worker threads, which does not work with Wallaby. Wallaby already parallelizes your test run in its own worker processes, so running in worker threads should not be necessary.
We've updated Wallaby to ignore this setting, which we believe will fix your problem.
Please update to the latest version of Wallaby core, v1.0.1391
.
If for some reason you are still having problems after updating, could you please create a small sample repo with the same structure and jest configuration as your project with a sample test that breaks in the same way?
Issue description or question
Wallaby tests were working fine, now they don't run, this error is shown:
Runtime error: Farm is ended, no more calls can be done to it.
To add more information, this is a pnpm monorepo and jest is installed in the root of the monorepo, instead of each workspace. It has been working fine for a while with this setup, until it didn't.
Wallaby diagnostics report