require() shouldn't be cached when the required files throws

[nicolo-ribaudo]

🐛 Bug Report

If a CJS file that throws is requried twice, the second time Jest doesn't throw but returns a cached result.

To Reproduce

See repo below

Expected behavior

Jest should throw both times, but the second time it returns the module.exports object defined by the requried module before throwing.

Link to repl or repo (highly encouraged)

https://github.com/nicolo-ribaudo/jest-bug-require-throws

envinfo

  System:
    OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 14.16.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.11 - /usr/local/bin/npm
  npmPackages:
    jest: ^27.0.0-next.6 => 27.0.0-next.6 

Context

I found this while trying to work around #11258, but it's not related to ESM.

[SimenB]

Oh, interesting! It's been that way for years and years 😃 Should be pretty straightforward to fix, tho (just removing the module from the cache in a catch then rethrowing

[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.