Process completed with exit code 1.

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

fatal error: rados/librados.h: No such file or directory

Process completed with exit code 1.

fatal error: rados/librados.h: No such file or directory

could not import fmt (open $WORK/b066/_pkg_.a: no such file or directory)

could not import context (open $WORK/b063/_pkg_.a: no such file or directory)

could not import sync/atomic (open $WORK/b040/_pkg_.a: no such file or directory)

could not import os (open $WORK/b003/_pkg_.a: no such file or directory)

could not import fmt (open $WORK/b066/_pkg_.a: no such file or directory)

could not import sync/atomic (open $WORK/b040/_pkg_.a: no such file or directory)

could not import sync/atomic (open $WORK/b040/_pkg_.a: no such file or directory)

could not import internal/coverage/cfile (open $WORK/b123/_pkg_.a: no such file or directory)

could not import os (open $WORK/b003/_pkg_.a: no such file or directory)

fatal error: rados/librados.h: No such file or directory

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@0a12ed9d6a96ab950c8f026ed9f722fe0da7ef32. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 restore: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@0a12ed9d6a96ab950c8f026ed9f722fe0da7ef32. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 restore: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@0a12ed9d6a96ab950c8f026ed9f722fe0da7ef32, actions/setup-node@v4, actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/