Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No available formula with the name "llvm@5". Did you mean llvm, llvm@15, llm, llvm@21, llvm@20, llvm@19, llvm@18, llvm@17, llvm@16, llvm@14, llvm@12 or wllvm?

llvm@20 was installed but not linked because llvm@18 is already installed. To link this version, run: brew link llvm@20

No available formula with the name "llvm@5". Did you mean llvm, llvm@15, llm, llvm@21, llvm@20, llvm@19, llvm@18, llvm@17, llvm@16, llvm@14, llvm@12 or wllvm?

llvm@20 was installed but not linked because llvm@15 is already installed. To link this version, run: brew link llvm@20

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to add apt key via download https://bazel.build/bazel-release.pub.gpg: Error: Failed to install apt packages: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' Error: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' at Error (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/lib/error.js:60:11) at parsed (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:209:4) at R (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:286:26) at F (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/src/root.mts:73:5) at updateAptRepos (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/update.ts:14:15) at call (/home/runner/work/setup-cpp/setup-cpp/node_modules/memoizee/lib/configure-map.js:80:41) at installAptPack (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/install.ts:88:27) at addAptKeyViaURL (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/apt-key.ts:115:27) at setupBazel (/home/runner/work/setup-cpp/setup-cpp/src/bazel/bazel.ts:32:29) at Object.<anonymous> (/home/runner/work/setup-cpp/setup-cpp/src/bazel/__tests__/bazel.test.ts:14:25)

Failed to add apt key via download https://bazel.build/bazel-release.pub.gpg: Error: Failed to install apt packages: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' Error: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' at Error (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/lib/error.js:60:11) at parsed (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:209:4) at R (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:286:26) at F (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/src/root.mts:73:5) at updateAptRepos (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/update.ts:14:15) at call (/home/runner/work/setup-cpp/setup-cpp/node_modules/memoizee/lib/configure-map.js:80:41) at installAptPack (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/install.ts:88:27) at addAptKeyViaURL (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/apt-key.ts:115:27) at setupBazel (/home/runner/work/setup-cpp/setup-cpp/src/bazel/bazel.ts:32:29) at Object.<anonymous> (/home/runner/work/setup-cpp/setup-cpp/src/bazel/__tests__/bazel.test.ts:14:25)

No available formula with the name "llvm@5". Did you mean llvm, llvm@15, llm, llvm@21, llvm@20, llvm@19, llvm@18, llvm@17, llvm@16, llvm@14, llvm@12 or wllvm?

llvm@15 was installed but not linked because llvm@18 is already installed. To link this version, run: brew link llvm@15

Failed to download doxygen binary. Error: Doxygen binaries are not available for Linux arm64. Falling back to installing the latest version from apt-get.

pipx was not installed completely for the system-wide python: Error: Failed to install apt packages: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' Error: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' at Error (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/lib/error.js:60:11) at parsed (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:209:4) at R (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:286:26) at F (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/src/root.mts:73:5) at updateAptRepos (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/update.ts:14:15) at call (/home/runner/work/setup-cpp/setup-cpp/node_modules/memoizee/lib/configure-map.js:80:41) at installAptPack (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/install.ts:88:27) at setupPipPackSystem (/home/runner/work/setup-cpp/setup-cpp/src/utils/setup/setupPipPack.ts:295:28) at setupPipx (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:75:33) at processTicksAndRejections (node:internal/process/task_queues:105:5) at setupPython (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:59:3) at Object.<anonymous> (/home/runner/work/setup-cpp/setup-cpp/src/python/__tests__/python.test.ts:30:25)

Failed to download doxygen binary. Error: Doxygen binaries are not available for Linux arm64. Falling back to installing the latest version from apt-get.

pipx was not installed completely for the system-wide python: Error: Failed to install apt packages: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' Error: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' at Error (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/lib/error.js:60:11) at parsed (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:209:4) at R (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:286:26) at F (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/src/root.mts:73:5) at updateAptRepos (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/update.ts:14:15) at call (/home/runner/work/setup-cpp/setup-cpp/node_modules/memoizee/lib/configure-map.js:80:41) at installAptPack (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/install.ts:88:27) at setupPipPackSystem (/home/runner/work/setup-cpp/setup-cpp/src/utils/setup/setupPipPack.ts:295:28) at setupPipx (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:75:33) at processTicksAndRejections (node:internal/process/task_queues:105:5) at setupPython (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:59:3) at Object.<anonymous> (/home/runner/work/setup-cpp/setup-cpp/src/python/__tests__/python.test.ts:30:25)

Failed to download doxygen binary. Error: Failed to download doxygen x64 from https://www.doxygen.nl/files/doxygen-.linux.bin.tar.gz: Error: Unexpected HTTP response: 404. Falling back to installing the latest version from apt-get.

pipx was not installed completely for the system-wide python: Error: Failed to install apt packages: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' Error: Command failed with exit code 100: sudo 'apt-fast' 'update' '-o' 'Dpkg::Lock::Timeout=300' at Error (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/lib/error.js:60:11) at parsed (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:209:4) at R (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/node_modules/.pnpm/execa@7.2.0/node_modules/execa/index.js:286:26) at F (/home/runner/work/setup-cpp/setup-cpp/node_modules/admina/src/root.mts:73:5) at updateAptRepos (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/update.ts:14:15) at call (/home/runner/work/setup-cpp/setup-cpp/node_modules/memoizee/lib/configure-map.js:80:41) at installAptPack (/home/runner/work/setup-cpp/setup-cpp/packages/setup-apt/src/install.ts:88:27) at setupPipPackSystem (/home/runner/work/setup-cpp/setup-cpp/src/utils/setup/setupPipPack.ts:295:28) at setupPipx (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:75:33) at processTicksAndRejections (node:internal/process/task_queues:105:5) at setupPython (/home/runner/work/setup-cpp/setup-cpp/src/python/python.ts:59:3) at Object.<anonymous> (/home/runner/work/setup-cpp/setup-cpp/src/python/__tests__/python.test.ts:30:25)

Failed to download doxygen binary. Error: Failed to download doxygen x64 from https://www.doxygen.nl/files/doxygen-.linux.bin.tar.gz: Error: Unexpected HTTP response: 404. Falling back to installing the latest version from apt-get.