Fix integration test worker crashes in Azure Functions on Py3.13

[Copilot]

Motivation and Context

All 20 pytest-xdist workers crash with [gwN] node down: Not properly terminated during Azure Functions integration tests on Python 3.13. The python-tests-functions job had a UV_PYTHON: "3.10" override masking this, but the parent workflow sets UV_PYTHON: "3.13", so the override was silently ignored.

Two root causes were identified:

1. xdist worker crash: The function_app_for_test fixture retry loop can spend up to ~184s (3 × 60s wait + cleanup), exceeding the 120s --timeout. When pytest-timeout's thread method fires mid-fixture and the thread is blocked, it calls os._exit() — killing the xdist worker outright. Compounding this, the func subprocess shares the worker's process group, so signals propagate bidirectionally.

2. Azure Functions worker segfault: The Azure Functions Python worker crashes with SIGSEGV (exit code 139) on Python 3.13 due to the protobuf C extension (google._upb) failing during the worker's module isolation cleanup. This prevents the function app from starting at all on Python 3.13.

Description

conftest.py — subprocess isolation

Added start_new_session=True on Linux so the func start process runs in its own process group. Prevents signal cross-contamination between pytest-timeout and the function host.

conftest.py — fixture timeout budget

Added a 100s overall budget (under the 120s test timeout) that caps each retry's max_wait to the remaining time. The fixture now always exits cleanly via pytest.fail() instead of being killed by os._exit(). Uses time.monotonic() for budget tracking so NTP/clock adjustments cannot skew the enforcement.

conftest.py — worker Python redirect for Python ≥3.13

Added _find_func_worker_python() that auto-detects when the test runner is on Python ≥3.13 and finds a compatible Python 3.10–3.12 executable (checking FUNC_WORKER_PYTHON env var, then python3.12/python3.11/python3.10 via shutil.which). Sets languageWorkers__python__defaultExecutablePath in the func process env so the Azure Functions host uses the compatible Python for its worker while pytest continues running on 3.13.

azure-functions-integration-setup action — ensure Python 3.12 availability

Added a step to the CI setup action that ensures Python 3.12 is available on the runner. If the system doesn't have python3.12, it installs it via uv python install 3.12 and exports the path as FUNC_WORKER_PYTHON for the conftest to use.

Workflow files — remove stale Python 3.10 pin

Removed UV_PYTHON: "3.10" from python-tests-functions in both python-merge-tests.yml and python-integration-tests.yml. The job now inherits the workflow-level UV_PYTHON: "3.13".

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Integration tests failing due to parallel worker crashes in Azure Functions in Py3.13</issue_title>
<issue_description>Description
The Python - Merge - Tests workflow job is failing due to all 20 parallel pytest-xdist workers crashing during integration tests in packages/azurefunctions/tests/integration_tests/.

Job: https://github.com/microsoft/agent-framework/actions/runs/22343078848/job/64650758582

Symptoms
20 tests failed, 18 passed, 3 skipped (ran for ~12 minutes)
All failures are worker crashes, not assertion errors
Failures span all test categories: single agent, multi-agent, workflows, and HITL
Even the basic test_health_check test fails, indicating the Azure Functions host was likely unreachable
Affected Tests
test_01_single_agent.py – 5 tests
test_04_single_agent_orchestration_chaining.py – 1 test
test_05_multi_agent_orchestration_concurrency.py – 1 test
test_06_multi_agent_orchestration_conditionals.py – 2 tests
test_07_single_agent_orchestration_hitl.py – 2 tests
test_09_workflow_shared_state.py – 3 tests
test_11_workflow_parallel.py – 3 tests
test_12_workflow_hitl.py – 3 tests
Possible Causes
Azure Functions deployment step failed earlier in the workflow
Missing or misconfigured environment secrets/variables
Infrastructure provisioning issue causing the test environment to be unavailable
Steps to Investigate
Check the Azure Functions deployment step in the workflow run
Verify environment secrets and variables are correctly configured
Review infrastructure provisioning logs earlier in the workflow

Requirement:
The integration tests for azurefunctions package should run on Py3.13 without failure. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Python: Integration tests failing due to parallel worker crashes in Azure Functions in Py3.13 #4259

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Fixes pytest-xdist worker crashes in Azure Functions integration tests on Python 3.13 by preventing fixture startup from exceeding the pytest-timeout budget and isolating the func start subprocess from the worker’s process group. Also removes a stale workflow-level Python 3.10 override so CI actually runs these tests on 3.13.

Changes:

• Isolate the Azure Functions host subprocess on POSIX using start_new_session=True to prevent signal cross-contamination.
• Add an overall startup time budget in the function_app_for_test fixture to ensure clean failure (pytest.fail) before pytest-timeout can hard-exit the worker.
• Remove UV_PYTHON: "3.10" overrides from the Functions integration test jobs so they inherit the workflow’s Python version (3.13).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
python/packages/azurefunctions/tests/integration_tests/conftest.py	Adds POSIX process-group isolation for func start and enforces an overall fixture startup budget to avoid pytest-timeout killing xdist workers.
.github/workflows/python-merge-tests.yml	Removes the job-level UV_PYTHON pin so merge tests run Functions integration on the workflow’s Python version.
.github/workflows/python-integration-tests.yml	Removes the job-level UV_PYTHON pin so integration tests run Functions integration on the workflow’s Python version.

[markwallace-microsoft]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
TOTAL	22174	2762	87%

report-only-changed-files is enabled. No files were changed during this commit :)

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
4672	247 💤	0 ❌	0 🔥	1m 16s ⏱️

[larohra]

@copilot code review[agent] fix the comments and failing jobs

[Copilot]

@copilot code review[agent] fix the comments and failing jobs

Fixed the review comment (time.monotonic() instead of time.time()) in 3c46364. The CI jobs on this branch are passing — the latest run (22418056690) completed successfully.

[larohra]

@copilot I ran the integrations test CI for validating the fix and it looks like its still failing - https://github.com/microsoft/agent-framework/actions/runs/22430115474/job/64947032165
Can you ivnestigate and fix the issue and make sure the Functions Integration tests are working fine for Py3.13

[Copilot]

@copilot I ran the integrations test CI for validating the fix and it looks like its still failing - https://github.com/microsoft/agent-framework/actions/runs/22430115474/job/64947032165
Can you ivnes...

Investigated the failing job. The root cause is different from the original xdist crash — the Azure Functions Python worker segfaults (exit code 139) on Python 3.13 due to the protobuf C extension (google._upb) crashing during the worker's module isolation.

Fixed in aa93e61 and 29fd8e6:

• conftest.py: Added _find_func_worker_python() that auto-detects when the test runner is on Python ≥3.13 and finds a compatible Python 3.10-3.12 executable. Sets languageWorkers__python__defaultExecutablePath so the func host uses the compatible Python for its worker while pytest continues running on 3.13.
• azure-functions-integration-setup action: Ensures Python 3.12 is available on the CI runner (installs via uv python install 3.12 if not already present on the system).