Skip to content

Python Integration Tests #29042

Python Integration Tests

Python Integration Tests #29042

Triggered via schedule March 29, 2026 00:48
Status Failure
Total duration 17m 42s
Artifacts
paths-filter
8s
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
4s
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: 0c1158a9-2ef8-4c13-9bc4-5193677d5600 Correlation ID: 50d5c8ff-49d4-4767-aea7-83257215ca99 Timestamp: 2026-03-29 00:53:13Z
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: 7f67121f-5520-4d0c-9c45-ca0c923d7f00 Correlation ID: 773dbf9d-ee48-485e-bf71-b297e99c7271 Timestamp: 2026-03-29 00:57:58Z
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: e205c430-19d6-48d6-8d43-7eaa1cc29b00 Correlation ID: 507eb843-9509-4b27-b1b4-d93267b02f51 Timestamp: 2026-03-29 01:03:34Z
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/