Move from "process.exit" to "exit"

[mjesun]

Changing all process.exit to exit. This prevents sudden truncation of Jest output when finishing test execution, if the output information is too big (I've seen issues when the JSON output is above 256 KiB). As per the Node docs, process.exit() will not wait up until all buffers are flushed, and will try to quit as soon as possible.

Tests are still passing since exit uses process.exit underneath.

[codecov-io]

Codecov Report

Merging #5313 into master will increase coverage by 0.03%.
The diff coverage is 30%.

@@            Coverage Diff             @@
##           master    #5313      +/-   ##
==========================================
+ Coverage   61.24%   61.27%   +0.03%     
==========================================
  Files         205      205              
  Lines        6892     6893       +1     
  Branches        3        4       +1     
==========================================
+ Hits         4221     4224       +3     
+ Misses       2670     2668       -2     
  Partials        1        1

Impacted Files	Coverage Δ
packages/jest-runner/src/test_worker.js	0% <ø> (ø)	⬆️
packages/jest-cli/src/watch.js	70.25% <0%> (ø)	⬆️
packages/jest-cli/src/test_scheduler.js	26.81% <0%> (+1.26%)	⬆️
packages/jest-cli/src/reporters/coverage_worker.js	50% <0%> (ø)	⬆️
packages/jest-cli/src/reporters/notify_reporter.js	8.69% <0%> (ø)	⬆️
packages/jest-cli/src/run_jest.js	52.54% <100%> (ø)	⬆️
packages/jest-runner/src/index.js	39.13% <50%> (+1.35%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cdc048d...8242e40. Read the comment docs.

[cpojer]

Is it possible to test this somehow?

[mjesun]

Tests already do test that (to some extent). Some of them spy or mock process.exit (e.g. here), which de-facto means testing the correct completion plus the exit module, all at once.

[github-actions]

This pull request 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.