Improve babel-plugin-jest-hoist logic
#14241
liuxingbaoyunodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
17s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
22s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
56s
TypeScript Compatibility
5m 14s
Typecheck Examples and Tests
3m 53s
Lint
1m 52s
Validate Yarn dependencies and constraints
17s
Node LTS on Ubuntu with leak detection
43s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
21 errors and 45 warnings
|
TypeScript Compatibility:
packages/babel-plugin-jest-hoist/src/index.ts#L374
Unexpected nullable boolean value in conditional. Please handle the nullish case explicitly
|
|
TypeScript Compatibility
Process completed with exit code 1.
|
|
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6356) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:7263) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:11369) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Ubuntu with shard 3/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
|
|
should not transpile the transformer:
e2e/__tests__/globalSetup.test.ts#L168
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/globalSetup.test.ts:168:20)
|
|
Option showSeed › if showSeed is present in the config the report will show the seed:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
node:events:496
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:511:26)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:511:12)
[... lines matching original stack trace ...]
at process.processTimers (node:internal/timers:529:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v22.11.0
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:42:37)
|
|
collects coverage only from multiple specified files:
e2e/__tests__/coverageReport.test.ts#L66
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from multiple specified files 1`
- Snapshot - 7
+ Received + 0
- --------------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- --------------|---------|----------|---------|---------|-------------------
- All files | 100 | 100 | 100 | 100 |
- file.js | 100 | 100 | 100 | 100 |
- otherFile.js | 100 | 100 | 100 | 100 |
- --------------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:66:18)
|
|
Option randomize › --randomize changes report to output seed:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
node:events:496
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:511:26)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:511:12)
[... lines matching original stack trace ...]
at process.processTimers (node:internal/timers:529:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v22.11.0
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)
|
|
no tests found message is redirected to stderr:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\use-stderr-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/useStderr.test.ts:16:24)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:12869) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:14127) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:24927) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
macOS with shard 2/3 / Node v23.x
Final attempt failed. Child_process exited with error code 1
|
|
onlyFailures flag works in non-watch mode:
e2e/__tests__/onlyFailuresNonWatch.test.ts#L38
expect(received).toMatch(expected)
Expected substring: "FAIL __tests__/a.js"
Received string: "node:events:496·
throw er; // Unhandled 'error' event·
^···
Error: kill EPERM·
at ChildProcess.kill (node:internal/child_process:511:26)·
at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1000:17)·
at ChildProcessWorker.forceExit (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1005:33)·
at Timeout._onTimeout (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:567:16)·
at listOnTimeout (node:internal/timers:594:17)·
at process.processTimers (node:internal/timers:529:7)·
Emitted 'error' event on ChildProcess instance at:·
at ChildProcess.kill (node:internal/child_process:511:12)·
at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1000:17)·
[... lines matching original stack trace ...]·
at process.processTimers (node:internal/timers:529:7) {·
errno: -4048,·
code: 'EPERM',·
syscall: 'kill'·
}···
Node.js v22.11.0"
at Object.toMatch (e2e/__tests__/onlyFailuresNonWatch.test.ts:38:18)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6236) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6684) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:2468) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
|
Windows with shard 3/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
|
|
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Validate Yarn dependencies and constraints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with leak detection
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (1/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (4/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (3/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (2/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Typecheck Examples and Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
TypeScript Compatibility
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 3/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 3/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 2/3 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 2/3 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 3/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 3/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|