[Bug]: SIGNREQUEST incorrectly detected as an open handle

[cristianrgreco]

Version

28.0.3

Steps to reproduce

Run the following test via jest --detectOpenHandles:

const crypto = require('crypto');

test('should not detect open handles', () => {
  const key =
    '-----BEGIN PRIVATE KEY-----\r\nMC4CAQAwBQYDK2VwBCIEIHKj+sVa9WcD'
    + '/q2DJUJaf43Kptc8xYuUQA4bOFj9vC8T\r\n-----END PRIVATE KEY-----';

  const data = Buffer.from('a');

  const sig = crypto.sign(null, data, key);
});

Expected behavior

crypto.sign is a synchronous operation. Once the test completes, I would expect Jest to not detect any open handles.

Actual behavior

An open handle is detected:

> jest "--detectOpenHandles"

 PASS  ./test.js
  ✓ should not detect open handles (2 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.12 s, estimated 1 s
Ran all test suites.

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  SIGNREQUEST

       8 |   const data = Buffer.from('a');
       9 |
    > 10 |   const sig = crypto.sign(null, data, key);
         |                      ^
      11 | });
      12 |
      13 |

      at Object.sign (test.js:10:22)
      at TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:317:13)
      at runJest (node_modules/@jest/core/build/runJest.js:407:19)
      at _run10000 (node_modules/@jest/core/build/cli/index.js:338:7)
      at runCLI (node_modules/@jest/core/build/cli/index.js:190:3)

Additional context

No response

Environment

System:
  OS: Mac OS X 12.3.1 (21E258) / Ubuntu 20.04.4 LTS
  CPU: Apple M1 Max
Binaries:
  Node: v16.13.1 / v17.3.0
  NPM: 8.1.2

[SimenB]

Wanna send a PR? https://github.com/facebook/jest/blob/dd690ca905a9fab1901b1c96894dce28874c294a/packages/jest-core/src/collectHandles.ts#L65-L78

[cristianrgreco]

@SimenB Sure! Here it is: #12789.

[SimenB]

https://github.com/facebook/jest/releases/tag/v28.1.0

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