Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Not authorized to perform sts:AssumeRoleWithWebIdentity

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

The run was canceled by @huydhn.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

Not authorized to perform sts:AssumeRoleWithWebIdentity

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

[OSDC] Step cancelled by GitHub Actions (received SIGINT). This typically means matrix fail-fast, a manual cancel, a workflow concurrency override, or a run-level cancellation — NOT an OSDC infrastructure failure. Check the workflow-run page for the actual cause; the in-pod subprocess is terminated by the hook so post-cleanup steps can run.

received SIGINT

Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Process completed with exit code 1.

[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.

Not authorized to perform sts:AssumeRoleWithWebIdentity

The run was canceled by @huydhn.

The operation was canceled.

The run was canceled by @huydhn.

The operation was canceled.

The run was canceled by @huydhn.

The operation was canceled.

Process completed with exit code 1.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

The run was canceled by @huydhn.

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 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/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, nick-fields/retry@3e91a01664abd3c5cd539100d10d33b9c5b68482, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/

No files were found with the provided path: /__w/_temp/artifacts/. No artifacts will be uploaded.

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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, nick-fields/retry@3e91a01664abd3c5cd539100d10d33b9c5b68482, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, nick-fields/retry@3e91a01664abd3c5cd539100d10d33b9c5b68482, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/