chore(deps): update dependency @types/merge-stream to v2 (#15326) #14149
nodejs.yml
on: push
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
53s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 4s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 20s
TypeScript Compatibility
5m 44s
Typecheck Examples and Tests
4m 7s
Lint
1m 50s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
1m 9s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
11 errors and 10 warnings
can press "u" to update snapshots:
e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "u" to update snapshots: test results 1`
- Snapshot - 0
+ Received + 1
@@ -14,7 +14,8 @@
| ^
at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35)
› 1 snapshot failed.
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
Snapshot Summary
› 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them."
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
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)
|
--findRelatedTests flag › generates coverage report for filename:
node:internal/child_process#L511
Could not find test summary in the output.
OUTPUT:
PASS __tests__/a.test.js
✓ a (5 ms)
node:events:497
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.9.0
at extractSummary (e2e/Utils.ts:245:11)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:211:38)
|
--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`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles `Symbol`:
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 functions:
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 circular inequality properly:
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:56:35)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles circular inequality properly:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
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)
|
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 v22.x
Attempt 1 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
|
Node LTS on Ubuntu with coverage (1/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (2/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (3/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Node LTS on Ubuntu with coverage (4/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Windows with shard 4/4 / Node v22.x
Attempt 1 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
|