[Bug]: test "typescript - reads config from ts file when package.json#type=module" is flaky

[F3n67u]

Version

N/A

Steps to reproduce

The typescript config test needs @jest/types to be built. we run tsc -b packages/jest-types in beforeAll and set a 60s timeout, but this command run more than 60s occasionally at ci. I cannot reproduce it on my local macOS computer.

https://github.com/facebook/jest/runs/5465229008?check_suite_focus=true#step:8:7

Run yarn test-ci-partial:parallel --max-workers 3 --shard=3/[4](https://github.com/facebook/jest/runs/5465229008?check_suite_focus=true#step:8:4)
...........................................................
/Users/runner/work/jest/jest/e2e/__tests__/esmConfigFile.test.ts

  ● on node >=12.17.0 › typescript › reads config from ts file when package.json#type=module

    thrown: "Exceeded timeout of 60000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      [5](https://github.com/facebook/jest/runs/5465229008?check_suite_focus=true#step:8:5)0 |
      51 |   describe('typescript', () => {
    > 52 |     beforeAll(async () => {
         |     ^
      53 |       // the typescript config test needs `@jest/types` to be built
      54 |       const cwd = resolve(__dirname, '../../');
      55 |       const typesPackageDirectory = 'packages/jest-types';

      at beforeAll (e2e/__tests__/esmConfigFile.test.ts:52:5)
      at describe (e2e/__tests__/esmConfigFile.test.ts:51:3)
      at Object.<anonymous> (e2e/__tests__/esmConfigFile.test.ts:2[6](https://github.com/facebook/jest/runs/5465229008?check_suite_focus=true#step:8:6):1)

Setup MongoDB Test Environment
Teardown MongoDB Test Environment
..................................................

Error: Process completed with exit code 1.

Expected behavior

The test is timeout after 60s and failed.

Actual behavior

Test fail occasionly.fails

Additional context

No response

Environment

N/A

[SimenB]

This only started happening after #12521 (comment), no idea why. should probably revert it

[mrazauskas]

Can be just a timeout as well. tsc is not only building types, but is also running full check of declaration files. This can take a lot of time on slower machines. (While working on slow computer, I was keeping "skipLibCheck": true just to stay sane.)

@F3n67u Would you be interested to send a PR with simply increased timeout? Just to see.

[SimenB]

Happy to try out skiplibcheck for this test if applicable. Not for our actual type check, but this specific test would be fine 👍

[F3n67u]

I am wondering why not run yarn build instead of yarn build:js at ci to prepare everything?

[SimenB]

Since it takes 6-7 minutes to do

[F3n67u]

Can be just a timeout as well. tsc is not only building types, but is also running full check of declaration files. This can take a lot of time on slower machines. (While working on slow computer, I was keeping "skipLibCheck": true just to stay sane.)

@F3n67u Would you be interested to send a PR with simply increased timeout? Just to see.

I filed a pr to increase timeout to 360s: #12560

[F3n67u]

CI turn green when increase timeout to 360s, see https://github.com/facebook/jest/runs/5481848898?check_suite_focus=true

[F3n67u]

CI turn green when increase timeout to 360s, see https://github.com/facebook/jest/runs/5481848898?check_suite_focus=true

GitHub ci is green. but circle ci is failing bec another reason. https://app.circleci.com/pipelines/github/facebook/jest/7495/workflows/5cc9e009-a69d-4a37-afb5-6a210da76aa9/jobs/120954/parallel-runs/1/steps/1-109

[mrazauskas]

@F3n67u Thanks! It was just a timeout? Nice. Seems like currently tsc does not allow to use --build and --skipLibCheck flags together. At least I don’t know how to make it work. So perhaps increasing timeout is fine.

---

Regarding the other issue. Not sure if that’s the same problem, but running yarn jest --detectOpenHandles locally (Node 17, macOS 12, Apple M1) points to "examples/react-native". Here is what I see running yarn jest --projects examples/react-native --detectOpenHandles:

To be honest, I have no experience with React at all.

Perhaps it is worth to open a PR with "examples/react-native" removed (or disable)? Just to see if CircleCI will pass. If so, it would be clear where to look for the problem. I am just guessing again.