Version

27.5.1

Steps to reproduce

it('test1', () => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      throw new Error();
      resolve(1);
    });
  }).then((v) => expect(v).toBe(1));
});

Expected behavior

In this case, an error thrown in setTimeout interrupts the resolve(1) of the promise, so the promise will stay in <pending> state. However, I guess this "unwanted" error is expected to be presented to the user in some way.

Actual behavior

The error "disappears", without any hint on its existence. JEST simply stucks at running the test case (since the promise is never resolved), and ends after the default timeout is hit, and exits without any further information.

Additional context

No response

Environment

System:
    OS: Linux undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Binaries:
    Node: 14.17.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /bin/yarn
    npm: 7.17.0 - /bin/npm
npmPackages:
    jest: ^27.5.1 => 27.5.1