Python Integration Tests #29111
python-integration-tests.yml
on: schedule
paths-filter
9s
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
3s
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: b7dd37de-dfaa-49ca-8ddb-e9a41e752900 Correlation ID: 786122c2-a411-4c50-9fbe-ad7e31bacfb9 Timestamp: 2026-04-11 00:51:33Z
|
|
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: 5097c08d-0fdb-4f46-81da-111b7bca4000 Correlation ID: 0bf3a02e-5d0d-42cd-b4cc-b403068717dc Timestamp: 2026-04-11 00:57:38Z
|
|
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: 2d24d7f3-d023-4580-8b6d-0d68f5454200 Correlation ID: c33d54d0-b3ae-4e98-8348-c3d20c2de6f7 Timestamp: 2026-04-11 01:03:39Z
|
|
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/
|