Skip to content

Python Integration Tests #29053

Python Integration Tests

Python Integration Tests #29053

Triggered via schedule April 1, 2026 00:51
Status Failure
Total duration 6h 12m 29s
Artifacts
paths-filter
5s
paths-filter
Matrix: Python Integration Tests - Scheduled run
Matrix: Python Pre-Merge Integration Tests - Agents
Matrix: Python Pre-Merge Integration Tests - AI Services (incl samples using those)
Matrix: Python Pre-Merge Integration Tests - Memory (incl samples using those)
Matrix: Python Pre-Merge Integration Tests - Multi-Modality
Matrix: Python Pre-Merge Integration Tests - Ollama
python-integration-tests-check
6s
python-integration-tests-check
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 6 warnings
Python Integration Tests - Scheduled run (3.10, ubuntu-latest)
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Python Integration Tests - Scheduled run (3.10, ubuntu-latest)
Run the command below to authenticate interactively; additional arguments may be added as needed: az logout az login
Python Integration Tests - Scheduled run (3.10, ubuntu-latest)
AADSTS700213: No matching federated identity record found for presented assertion subject 'repository_owner_id:6154722:repository_id:607289185:ref:refs/heads/main'. Check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://learn.microsoft.com/entra/workload-id/workload-identity-federation Trace ID: 040629d9-2c06-4bfb-a451-11feebf20900 Correlation ID: faea49f4-fd7f-44da-8471-050df7c80f31 Timestamp: 2026-04-01 00:53:57Z
Python Integration Tests - Scheduled run (3.10, windows-latest)
Container operations are only supported on Linux runners
Python Integration Tests - Scheduled run (3.10, macos-latest)
docker: command not found
Python Integration Tests - Scheduled run (3.11, ubuntu-latest)
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Python Integration Tests - Scheduled run (3.11, ubuntu-latest)
Run the command below to authenticate interactively; additional arguments may be added as needed: az logout az login
Python Integration Tests - Scheduled run (3.11, ubuntu-latest)
AADSTS700213: No matching federated identity record found for presented assertion subject 'repository_owner_id:6154722:repository_id:607289185:ref:refs/heads/main'. Check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://learn.microsoft.com/entra/workload-id/workload-identity-federation Trace ID: 7a0c6d7e-b0a7-45c1-bd0a-a165069f0200 Correlation ID: 9113bb8e-b50c-4e97-8d35-a977ccb50a67 Timestamp: 2026-04-01 03:51:52Z
Python Integration Tests - Scheduled run (3.11, windows-latest)
Container operations are only supported on Linux runners
Python Integration Tests - Scheduled run (3.11, macos-latest)
docker: command not found
Python Integration Tests - Scheduled run (3.12, ubuntu-latest)
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Python Integration Tests - Scheduled run (3.12, ubuntu-latest)
Run the command below to authenticate interactively; additional arguments may be added as needed: az logout az login
Python Integration Tests - Scheduled run (3.12, ubuntu-latest)
AADSTS700213: No matching federated identity record found for presented assertion subject 'repository_owner_id:6154722:repository_id:607289185:ref:refs/heads/main'. Check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://learn.microsoft.com/entra/workload-id/workload-identity-federation Trace ID: 9b865800-a474-4b81-9fac-11fb20f40a00 Correlation ID: 59314a63-0ad9-4671-ab4c-7cbec92d78b8 Timestamp: 2026-04-01 05:56:47Z
Python Integration Tests - Scheduled run (3.12, windows-latest)
Container operations are only supported on Linux runners
Python Integration Tests - Scheduled run (3.12, macos-latest)
docker: command not found
python-integration-tests-check
Integration Tests Failed!
paths-filter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
paths-filter
'before' field is missing in event payload - changes will be detected from last commit
Python Integration Tests - Scheduled run (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: astral-sh/setup-uv@v6, aws-actions/configure-aws-credentials@v5, azure/login@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Python Integration Tests - Scheduled run (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: astral-sh/setup-uv@v6, aws-actions/configure-aws-credentials@v5, azure/login@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Python Integration Tests - Scheduled run (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: astral-sh/setup-uv@v6, aws-actions/configure-aws-credentials@v5, azure/login@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
python-integration-tests-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/