feat: add Dockerfile and docker-compose for dev env #14946
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
25s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
23s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
57s
TypeScript Compatibility
6m 2s
Typecheck Examples and Tests
4m 9s
Lint
1m 51s
Validate Yarn dependencies and constraints
38s
Node LTS on Ubuntu with leak detection
52s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
25 errors, 7 warnings, and 32 notices
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)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
gets changed files for hg:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
gets changed files for hg:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
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)
|
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:85:35)
|
processChild › handles `BigInt`:
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`:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles `Map`:
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:
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 circular inequality properly:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
|
processChild › handles functions:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles functions:
undefined#L0
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
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:111:35)
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v24.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 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 1/3 / Node v22.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v24.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 3/3 / Node v20.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
macOS with shard 2/3 / Node v18.x
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|