Process completed with exit code 1.

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in argument to (_Cfunc_instrument_hooks_write_environment)

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in argument to (_Cfunc_instrument_hooks_add_marker)

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in argument to (_Cfunc_instrument_hooks_add_marker)

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in argument to (_Cfunc_instrument_hooks_set_executed_benchmark)

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

The strategy configuration was canceled because "tests._1_24_x" failed

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

Process completed with exit code 1.

failed to execute the benchmark process: exit status: 1

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

The strategy configuration was canceled because "compat-integration-test-walltime.example" failed

Process completed with exit code 1.

failed to execute the benchmark process: exit status: 1

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

The strategy configuration was canceled because "compat-integration-test-walltime.example" failed

The operation was canceled.

failed to execute the benchmark process: exit status: 1

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

The strategy configuration was canceled because "compat-integration-test-walltime.example" failed

Process completed with exit code 1.

failed to execute the benchmark process: exit status: 1

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

The strategy configuration was canceled because "compat-integration-test-walltime.example" failed

Process completed with exit code 1.

failed to execute the benchmark process: exit status: 1

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint32_t(pid) (value of uint32 type _Ctype_uint32_t) as _Ctype_int32_t value in variable declaration

cannot use _Ctype_uint(pid) (value of uint32 type _Ctype_uint) as _Ctype_int32_t value in variable declaration

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: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5. 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 restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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: actions/checkout@v4. 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: actions/checkout@v4. 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: actions/checkout@v4, actions/setup-go@v5. 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/

Error running rustup toolchain list, falling back to default toolchain only: Error: The process '/home/runner/.cargo/bin/rustup' failed with exit code 1

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/

Error running rustup toolchain list, falling back to default toolchain only: Error: The process '/home/runner/.cargo/bin/rustup' failed with exit code 1

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/

Error running rustup toolchain list, falling back to default toolchain only: Error: The process '/home/runner/.cargo/bin/rustup' failed with exit code 1

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/

Error running rustup toolchain list, falling back to default toolchain only: Error: The process '/home/runner/.cargo/bin/rustup' failed with exit code 1

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/

Error running rustup toolchain list, falling back to default toolchain only: Error: The process '/home/runner/.cargo/bin/rustup' failed with exit code 1

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/