watchAll mode uses all available cores

[brapifra]

🐛 Bug Report

According to the docs, jest uses half of the available cores by default when in watch mode to ensure that it is unobtrusive and does not grind the machine to a halt. This is true for the --watch mode, but it is still using all the availables cores - 1 in the --watchAll mode.

To Reproduce

Steps to reproduce the behavior:

1. Execute jest with --watchAll flag
2. You can then observe that the number of workers created is equals to NUMBER_OF_CORES - 1.

Expected behavior

By default, it should only use half of the available cores of the machine to ensure that it is unobtrusive.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.