[Bug]: Jest 30 beta 4 causes AbortSignal.timeout to be undefined

[lencioni]

Version

30.0.0-beta.4

Steps to reproduce

1. Clone repo at https://github.com/lencioni/jest-abortsignal-timeout-bug
2. Run yarn install
3. Run yarn jest

You may need to run tests more than once to reproduce.

Expected behavior

I expect the tests to consistently pass.

Actual behavior

The second test will often tail because AbortSignal.timeout ends up being undefined.

 PASS  __tests__/2.test.js
 FAIL  __tests__/1.test.js
  ● has AbortSignal.timeout

    expect(received).toBeDefined()

    Received: undefined

      1 | it("has AbortSignal.timeout", () => {
    > 2 |   expect(AbortSignal.timeout).toBeDefined();
        |                               ^
      3 | });
      4 |

      at Object.toBeDefined (__tests__/1.test.js:2:31)

Test Suites: 1 failed, 1 passed, 2 total
Tests:       1 failed, 1 passed, 2 total
Snapshots:   0 total
Time:        0.105 s, estimated 1 s

 PASS  __tests__/1.test.js
 FAIL  __tests__/2.test.js
  ● has AbortSignal.timeout

    expect(received).toBeDefined()

    Received: undefined

      1 | it("has AbortSignal.timeout", () => {
    > 2 |   expect(AbortSignal.timeout).toBeDefined();
        |                               ^
      3 | });
      4 |

      at Object.toBeDefined (__tests__/2.test.js:2:31)

Test Suites: 1 failed, 1 passed, 2 total
Tests:       1 failed, 1 passed, 2 total
Snapshots:   0 total
Time:        0.139 s, estimated 1 s

Additional context

No response

Environment

System:
    OS: macOS 15.4.1
    CPU: (8) arm64 Apple M3
  Binaries:
    Node: 22.16.0 - ~/.local/share/mise/installs/node/22.16.0/bin/node
    Yarn: 1.22.22 - ~/.local/share/mise/installs/yarn/1.22.22/bin/yarn
    npm: 10.9.2 - ~/.local/share/mise/installs/node/22.16.0/bin/npm
  npmPackages:
    jest: 30.0.0-beta.4 => 30.0.0-beta.4

[mrazauskas]

Could this be related with #15632?

[lencioni]

Seems likely! I am also unable to reproduce this on 30.0.0-alpha.7, so I am guessing that it is the same root cause.

[lencioni]

I also tried the changes from the proposed fix #15636 and it does not resolve this issue for me. FYI @eyalroth

[mrazauskas]

Great news! Thanks for trying out the changes.

[cpojer]

Thanks for testing, and highlighting this issue. 30.0.0-beta.5 was released with the fix.

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