Skip to content

chore: update website deps #14365

chore: update website deps

chore: update website deps #14365

Triggered via pull request January 17, 2025 07:33
Status Failure
Total duration 17m 25s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
54s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
55s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 26s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 32s
TypeScript Compatibility
Typecheck Examples and Tests
4m 8s
Typecheck Examples and Tests
Lint
1m 43s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
46s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 44 warnings
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -27,21 +27,21 @@ START "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "three" + END: "one" at log (__tests__/concurrent.test.js:15:11) console.log START "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "one" + END: "three" at log (__tests__/concurrent.test.js:15:11) console.log START "seven" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
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)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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
EBUSY: resource busy or locked, rmdir '\\?\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)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -67,21 +67,21 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" at log (__tests__/concurrent.test.js:15:11) console.log END: "six" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 3 + Received + 3 @@ -82,21 +82,21 @@ END: "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "six" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
Windows with shard 3/4 / Node v20.x
Final attempt failed. Child_process exited with error code 1
with only › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L66
expect(received).toMatchSnapshot() Snapshot name: `with only runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -22,16 +22,16 @@ END: "nine" at log (__tests__/concurrent-only.test.js:15:11) console.log - END: "six" + END: "four" at log (__tests__/concurrent-only.test.js:15:11) console.log - END: "four" + END: "six" at log (__tests__/concurrent-only.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:66:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
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)
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)
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)
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)
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 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 v22.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 (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 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 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 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 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
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 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 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 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 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 v22.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 (3/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)
Attempt 1 failed. Reason: Child_process exited with error code 1
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 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 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 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 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 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 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 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 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 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
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 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
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 v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v16.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
Windows with shard 4/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1