The deploy step encountered an error: There was an error creating the worktree: The process '/usr/bin/git' failed with exit code 128 ❌ ❌

stderr: (node:3700) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

stderr: (node:3724) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

stderr: (node:3773) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

stderr: (node:3785) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

35435 stderr: (node:3797) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

40827 stderr: (node:3856) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

42635 stderr: (node:3881) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

41865 stderr: (node:3946) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

44765 stderr: (node:3971) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

40795 stderr: (node:4029) Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set. (Use `node --trace-warnings ...` to show where the warning was created)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, pnpm/action-setup@v2, JamesIves/[email protected], tsickert/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

workspace/waku/waku/[firefox] › multi-platform.spec.ts took 55.0s

workspace/waku/waku/[chromium] › multi-platform.spec.ts took 54.9s

workspace/waku/waku/[webkit] › multi-platform.spec.ts took 54.9s

workspace/waku/waku/[chromium] › examples-smoke.spec.ts took 38.8s

workspace/waku/waku/[firefox] › examples-smoke.spec.ts took 37.4s

workspace/waku/waku/[firefox] › multi-platform.spec.ts took 55.0s

workspace/waku/waku/[chromium] › multi-platform.spec.ts took 54.9s

workspace/waku/waku/[webkit] › multi-platform.spec.ts took 54.9s

workspace/waku/waku/[chromium] › examples-smoke.spec.ts took 38.8s

workspace/waku/waku/[firefox] › examples-smoke.spec.ts took 37.4s

2 failed [firefox] › create-waku.spec.ts:8:1 › should create waku with default setup work ─────────────── [webkit] › create-waku.spec.ts:8:1 › should create waku with default setup work ──────────────── 1 flaky [webkit] › ssr-swr.spec.ts:51:5 › ssr-swr: dev › increase counter ────────────────────────────── 15 skipped 285 passed (18.3m)