updated jsdom to 25.0.1 - fixes Deprecation warning for 'punycode' #14249
hutzelknechtnodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
1m 3s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 9s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 38s
TypeScript Compatibility
5m 32s
Typecheck Examples and Tests
3m 52s
Lint
1m 55s
Validate Yarn dependencies and constraints
12s
Node LTS on Ubuntu with leak detection
46s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
25 errors and 44 warnings
|
Validate Yarn dependencies and constraints
Process completed with exit code 1.
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6338) 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:7237) 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:11346) 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
|
|
--findRelatedTests flag › coverage configuration is applied correctly:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (4 ms)
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 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 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__/findRelatedFiles.test.ts:244:43)
|
|
--findRelatedTests flag › coverage configuration is applied correctly:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
|
|
processChild › handles `Symbol`:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:98:35)
|
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:12938) 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:14215) 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:25004) 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
|
|
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:6924) 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:4788) 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:3700) 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
|
|
processChild › handles `Map`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles `Map`:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
|
|
processChild › handles `BigInt`:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:72:35)
|
|
processChild › handles functions:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles functions:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
|
|
processChild › handles mixed structure:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:111:35)
|
|
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 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 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 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 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 v16.x
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 v18.x
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 (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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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
|
|
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 2/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node v16.x
Attempt 1 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
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
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
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|