Skip to content

fix(general): CRASH add exception handling for logging configuration #16751

fix(general): CRASH add exception handling for logging configuration

fix(general): CRASH add exception handling for logging configuration #16751

Re-run triggered March 17, 2026 08:55
Status Failure
Total duration 7m 20s
Artifacts

pr-test.yml

on: pull_request
Matrix: cdk-integration-tests-old-python
Matrix: cdk-integration-tests
Matrix: integration-tests-old-python
Matrix: integration-tests
Matrix: sast-integration-tests-old-python
Matrix: sast-integration-tests
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 94 warnings
mypy / mypy
Process completed with exit code 1.
unit-tests (3.11)
Process completed with exit code 1.
unit-tests (3.13)
The strategy configuration was canceled because "unit-tests._3_11" failed
unit-tests (3.13)
The operation was canceled.
unit-tests (3.10)
The strategy configuration was canceled because "unit-tests._3_11" failed
unit-tests (3.10)
The operation was canceled.
unit-tests (3.12)
The strategy configuration was canceled because "unit-tests._3_11" failed
unit-tests (3.12)
The operation was canceled.
unit-tests (3.9)
The strategy configuration was canceled because "unit-tests._3_11" failed
unit-tests (3.9)
The operation was canceled.
danger-check
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e. 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/
eval-keys-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, tj-actions/changed-files@ed68ef82c095e0d48ec87eccea555d944a631a4c. 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/
cfn-lint
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, tj-actions/changed-files@ed68ef82c095e0d48ec87eccea555d944a631a4c. 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/
cdk-integration-tests (3.12, macos-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
cdk-integration-tests (3.12, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NBe5aQAAAACPX+dmIVoCRbIaeTPAtL4eUEhMMzBFREdFMDIxOQBFZGdl
cdk-integration-tests (3.12, macos-latest)
Failed to restore: Cache service responded with 400
cdk-integration-tests (3.13, macos-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
cdk-integration-tests (3.13, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ORe5aQAAAACzJrAflatYSpqq2GJmVfhqUEFPRURHRTA2MTQARWRnZQ==
cdk-integration-tests (3.13, macos-latest)
Failed to restore: Cache service responded with 400
cdk-integration-tests (3.13, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
cdk-integration-tests (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0PBe5aQAAAACPROIfXEcVSrc8+nB+ckKMQ0hJMzBFREdFMDExMQBFZGdl
cdk-integration-tests (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
sast-integration-tests (3.12, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
sast-integration-tests (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pxe5aQAAAABfualfoORMQqIs23T2IQGsUEhYMzFFREdFMDUxNQBFZGdl
sast-integration-tests (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
sast-integration-tests (3.13, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
sast-integration-tests (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QRe5aQAAAAA5OHB5KekbTLkRddOjtHx0UEFPRURHRTA2MTUARWRnZQ==
sast-integration-tests (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
sast-integration-tests (3.13, macos-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
sast-integration-tests (3.13, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RBe5aQAAAABcVQJPQei4ToOP+oCMgTsZUEFPRURHRTA1MjIARWRnZQ==
sast-integration-tests (3.13, macos-latest)
Failed to restore: Cache service responded with 400
cdk-integration-tests (3.12, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
cdk-integration-tests (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SBe5aQAAAABg7NH28jDuTrKP2AS9huecUEhMMzBFREdFMDQyMABFZGdl
cdk-integration-tests (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
cdk-integration-tests-old-python (3.9, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
cdk-integration-tests-old-python (3.9, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SRe5aQAAAABN7l+0LNIST7e31xWRgm3mQ0hHRURHRTE4MTUARWRnZQ==
cdk-integration-tests-old-python (3.9, ubuntu-latest)
Failed to restore: Cache service responded with 400
lint / pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/setup-python@65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236. 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/
sast-integration-tests (3.12, macos-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
sast-integration-tests (3.12, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YRe5aQAAAAAA54DybpPaS4qGs+ajW5StU04xRURHRTE5MTUARWRnZQ==
sast-integration-tests (3.12, macos-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.13, macos-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.13, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ahe5aQAAAADMKWuSea0AS5DJ0/DHZ419UEFPRURHRTA1MTAARWRnZQ==
integration-tests (3.13, macos-latest)
Failed to restore: Cache service responded with 400
mypy / mypy
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@b4ffde65f46336ab88eb53be808477a3936bae11, actions/setup-python@65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236. 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/
mypy / mypy
Failed to restore: Cache service responded with 400
integration-tests (3.11, ubuntu-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fRe5aQAAAAAqql/Crmj1Ro2Iuy9cXDHQUEhYMzFFREdFMDUxOABFZGdl
integration-tests (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
integration-tests-old-python (3.9, ubuntu-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests-old-python (3.9, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ihe5aQAAAACmkonI71OOTIeTOV+6cezYQ0hJMzBFREdFMDQyMQBFZGdl
integration-tests-old-python (3.9, ubuntu-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.10, ubuntu-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jxe5aQAAAACilO8WnypJRK4WMNM/Rhi6Q0hJMzBFREdFMDMwNwBFZGdl
integration-tests (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.12, ubuntu-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0lhe5aQAAAADTTaPLYroxTZXzKB0YZZtyQ0hJMzBFREdFMDIyMABFZGdl
integration-tests (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
sast-integration-tests-old-python (3.9, ubuntu-latest)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f. 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/
sast-integration-tests-old-python (3.9, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mBe5aQAAAACkoNKoImm7RpgfLN50bbwEUEFPRURHRTA2MDcARWRnZQ==
sast-integration-tests-old-python (3.9, ubuntu-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.12, windows-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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/
integration-tests (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zRe5aQAAAADRhnz2K7ExTb8gDFanIR5oREVOMzAxMDAwMTAzMDMzAEVkZ2U=
integration-tests (3.12, windows-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.10, windows-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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/
integration-tests (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zhe5aQAAAADNtBVNxJI+S7pfoWHyce8mUEhMMzBFREdFMDQxMQBFZGdl
integration-tests (3.10, windows-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.11, windows-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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/
integration-tests (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05Re5aQAAAADlpCb+ieaLQoYeaVpqZdMsQ0hJMzBFREdFMDQxMQBFZGdl
integration-tests (3.11, windows-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.13, ubuntu-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08xe5aQAAAADk8to11rq7QaYdRCHfntH0UEFPRURHRTA1MjAARWRnZQ==
integration-tests (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.13, windows-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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/
integration-tests (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08xe5aQAAAACW2BARaGckQb9voX5it7fJRE0yRURHRTA5MTUARWRnZQ==
integration-tests (3.13, windows-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.12, macos-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.12, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+Be5aQAAAACztOTtFLc7QrXimOD5leOXU04xRURHRTI5MDkARWRnZQ==
integration-tests (3.12, macos-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.11, macos-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.11, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+xe5aQAAAACfODSRib3uT4xBf3LGNBOeUEhMMzBFREdFMDIxNQBFZGdl
integration-tests (3.11, macos-latest)
Failed to restore: Cache service responded with 400
integration-tests (3.10, macos-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
integration-tests (3.10, macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Chi5aQAAAAAGM4ziR/aCTbfJE6vtxKQFUEFPRURHRTA2MDcARWRnZQ==
integration-tests (3.10, macos-latest)
Failed to restore: Cache service responded with 400
integration-tests-old-python (3.9, windows-latest)
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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/
integration-tests-old-python (3.9, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DRi5aQAAAAArgwLS/nPDQ7VMEvwVN8K3REVOMzAxMDAwMTAzMDQ1AEVkZ2U=
integration-tests-old-python (3.9, windows-latest)
Failed to restore: Cache service responded with 400
dogfood-tests
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
dogfood-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TRi5aQAAAAD05xemHZe8SLAM87KlA7A1UEFPRURHRTA1MjEARWRnZQ==
dogfood-tests
Failed to restore: Cache service responded with 400
performance-tests
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-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, actions/setup-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
performance-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ghi5aQAAAAAcjJzuOEhZRJ1QHoNrA+asQ0hJMzBFREdFMDExNgBFZGdl
performance-tests
Failed to restore: Cache service responded with 400
unit-tests (3.11)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
unit-tests (3.11)
Failed to restore: Cache service responded with 400
unit-tests (3.13)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
unit-tests (3.13)
Failed to restore: Cache service responded with 400
unit-tests (3.10)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
unit-tests (3.10)
Failed to restore: Cache service responded with 400
unit-tests (3.12)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
unit-tests (3.12)
Failed to restore: Cache service responded with 400
unit-tests (3.9)
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-python@39cd14951b08e74b54015e9e001cdefcf80e669f, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, imranismail/setup-kustomize@a76db1c6419124d51470b1e388c4b29476f495f1. 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/
unit-tests (3.9)
Failed to restore: Cache service responded with 400