Skip to content

feat(pydantic-ai): Add tool description to execute_tool spans #1717

feat(pydantic-ai): Add tool description to execute_tool spans

feat(pydantic-ai): Add tool description to execute_tool spans #1717

Triggered via pull request March 6, 2026 16:28
Status Success
Total duration 3m 52s
Artifacts 2

test-integrations-mcp.yml

on: pull_request
Matrix: MCP
All MCP tests passed
3s
All MCP tests passed
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 13 warnings
NameError: execute_tool_span is used but no longer imported: tests/integrations/pydantic_ai/test_pydantic_ai.py#L2482
The import of `execute_tool_span` was removed from the import statement, but line 2493 still calls `execute_tool_span("test_tool", {"arg": "value"}, None, "function")`. This will cause a `NameError: name 'execute_tool_span' is not defined` at runtime when the test executes.
Test will fail with NameError due to missing execute_tool_span import: tests/integrations/pydantic_ai/test_pydantic_ai.py#L2482
The diff removes the import of `execute_tool_span` from the import statement, but line 2493 still uses `execute_tool_span("test_tool", {"arg": "value"}, None, "function")`. This will cause a `NameError: name 'execute_tool_span' is not defined` when the test `test_update_execute_tool_span_with_none_result` runs.
MCP (3.14, ubuntu-22.04)
❌ Patch coverage check failed: 0.00% < target 80%
MCP (3.14t, ubuntu-22.04)
❌ Patch coverage check failed: 0.00% < target 80%
MCP (3.14t, ubuntu-22.04)
Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.14t, ubuntu-22.04)
Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.12, ubuntu-22.04)
❌ Patch coverage check failed: 0.00% < target 80%
MCP (3.12, ubuntu-22.04)
Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.12, ubuntu-22.04)
Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.10, ubuntu-22.04)
❌ Patch coverage check failed: 0.00% < target 80%
MCP (3.10, ubuntu-22.04)
Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.10, ubuntu-22.04)
Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.13, ubuntu-22.04)
❌ Patch coverage check failed: 0.00% < target 80%
MCP (3.13, ubuntu-22.04)
Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
MCP (3.13, ubuntu-22.04)
Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Artifacts

Produced during runtime
Name Size Digest
codecov-coverage-results-ep-add-tool-description-to-pydantic-ai-spans-test-mcp
105 KB
sha256:a32e2c918918893d731ff7441d0d292286c2f02f61f3e5fe5762c705c4b02ff9
codecov-test-results-ep-add-tool-description-to-pydantic-ai-spans-test-mcp
232 Bytes
sha256:be8e7a2c76f90301c1051e9a935ff0a6c0d0b9fc279140e0f7021a34bedc9711