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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4, actions/cache/save@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Cache save failed.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Cache save failed.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Cache save failed.

CI measurement regression threshold exceeded

CI measurement regression threshold exceeded

CI measurement regression threshold exceeded

CI measurement regression threshold exceeded

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

[ci] devenv tasks run test:run --mode before failed after 158 s without a detected transient Nix failure

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/cache/restore@v4, actions/cache/save@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Cache save failed.

Failed to restore: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. RequestId:7e4ecbed-501e-003f-4b56-fa1202000000 Time:2026-06-12T10:33:30.9875368Z

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. RequestId:022d2858-201e-008a-7457-fac335000000 Time:2026-06-12T10:34:15.3678011Z

CI measurement comparison is partial because one or more enabled observations are not gateable

CI measurement comparison is partial because one or more enabled observations are not gateable

CI measurement comparison is partial because one or more enabled observations are not gateable

[ci] completed devenv tasks run lint:check --mode before in 79 s

[ci] devenv tasks run lint:check --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run lint:check --mode before (attempt 1/10)

[ci] completed devenv tasks run test:restate-integration --mode before in 106 s

[ci] devenv tasks run test:restate-integration --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run test:restate-integration --mode before (attempt 1/10)

[ci] completed devenv tasks run test:notion-integration --mode before in 106 s

[ci] devenv tasks run test:notion-integration --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run test:notion-integration --mode before (attempt 1/10)

[ci] completed devenv tasks run ts:check:strict --mode before in 22 s

[ci] starting devenv tasks run ts:check:strict --mode before (attempt 1/10)

[ci] completed devenv tasks run otel:test --mode before in 86 s

[ci] devenv tasks run otel:test --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run otel:test --mode before (attempt 1/10)

[ci] completed Cold pnpm deps validation in 145 s

[ci] Cold pnpm deps validation still running after 120 s (attempt 1/10)

[ci] Cold pnpm deps validation still running after 60 s (attempt 1/10)

[ci] starting Cold pnpm deps validation (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 120 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run test:run --mode before (attempt 1/10)

[ci] completed devenv tasks run netlify:deploy --show-output --input type=pr --input pr=775 --mode before in 120 s

[ci] devenv tasks run netlify:deploy --show-output --input type=pr --input pr=775 --mode before still running after 120 s (attempt 1/10)

[ci] devenv tasks run netlify:deploy --show-output --input type=pr --input pr=775 --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run netlify:deploy --show-output --input type=pr --input pr=775 --mode before (attempt 1/10)

[ci] completed devenv tasks run nix:check --mode before in 226 s

[ci] devenv tasks run nix:check --mode before still running after 180 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 120 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run nix:check --mode before (attempt 1/10)

[ci] completed Cold pnpm deps validation in 142 s

[ci] Cold pnpm deps validation still running after 120 s (attempt 1/10)

[ci] Cold pnpm deps validation still running after 60 s (attempt 1/10)

[ci] starting Cold pnpm deps validation (attempt 1/10)

paired wall-clock baseline prepared at /home/runner/work/_temp/ci-measurement-base (3a397f7f05cb129a55f42ed38a5f5543b0c9bfde)

CI measurement comparison is partial because one or more enabled observations are not gateable

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 24 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 22 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 21 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 20 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 23 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 22 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 21 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

downloaded 20 baseline artifact(s), but required observation counts are not satisfied yet; continuing through bounded candidate history

[ci] devenv tasks run test:run --mode before still running after 540 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 480 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 420 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 360 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 300 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 240 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 180 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 120 s (attempt 1/10)

[ci] devenv tasks run test:run --mode before still running after 60 s (attempt 1/10)

[ci] starting devenv tasks run test:run --mode before (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 555 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 495 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 435 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 375 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 315 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 255 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 195 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 120 s (attempt 1/10)

[ci] devenv tasks run nix:check --mode before still running after 60 s (attempt 1/10)