Skip to content

Commit 447ef0d

Browse files
authored
remove one python case (#13500)
1 parent fad9bc0 commit 447ef0d

File tree

2 files changed

+0
-29
lines changed

2 files changed

+0
-29
lines changed

tools/sdk-ai-bots/azure-sdk-qa-bot-evaluation/results/python-test.json

Lines changed: 0 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -146,34 +146,6 @@
146146
"response_completeness_reason": "The response is mostly complete, covering nearly all major points from the ground truth, but misses a few minor details and alternative suggestions.",
147147
"overall_score": 6.6
148148
},
149-
{
150-
"testcase": "Ubunty 2303 pypy39 specific failure",
151-
"expected": {
152-
"answer": "You have a dependency that doesn't ship a pypy39 dep. That's all. You could swap that with pypy311 in your matrix if you wanted to give it a shot.",
153-
"reference_urls": []
154-
},
155-
"actual": {
156-
"answer": "The error message in your pipeline\u2014\"the configured PyPy interpreter version (3.9) is lower than PyO3's minimum supported version (3.11)\"\u2014means that PyO3 (a Rust/Python interop library) now requires PyPy version 3.11 or higher, but your CI environment is using PyPy 3.9.\n\nTo resolve this, you need to update your CI configuration to use PyPy 3.11 or newer instead of PyPy 3.9. Python SDKs must support Python 3.8+ (see guidelines), but toolchains and dependencies like PyO3 may raise their minimum version requirements independently. The recommended action is:\n\n1. **Update your CI configuration**: Change the Python interpreter to PyPy 3.11 (or newer) where the build is running.\n2. **Verify your local and pipeline environment**: Make sure any references to PyPy 3.9 are updated in scripts, Dockerfiles, or pipeline YAML files to PyPy 3.11.\n3. **Check compatibility of your SDK code**: Most Azure Python SDKs are tested on CPython, but if you explicitly need PyPy, ensure your code and dependencies support the newer PyPy version.\n\nYou do not need to change PyO3 requirements (unless you want to fork/patch the dependency, which is not recommended). Instead, upgrading your interpreter is the best approach.\n\nIf your pipeline template installs PyPy using system packages or a version manager, update those steps accordingly. For more on supported Python versions for Azure SDK, see the guidelines below.",
157-
"reference_urls": [
158-
"https://azure.github.io/azure-sdk/python_design.html",
159-
"https://github.com/Azure/azure-sdk-for-python/wiki/Azure-SDKs-Python-version-support-policy"
160-
]
161-
},
162-
"similarity": 4.0,
163-
"gpt_similarity": 4.0,
164-
"similarity_result": "pass",
165-
"similarity_threshold": 4,
166-
"groundedness": NaN,
167-
"gpt_groundedness": NaN,
168-
"groundedness_reason": NaN,
169-
"groundedness_result": NaN,
170-
"groundedness_threshold": NaN,
171-
"response_completeness": 4.0,
172-
"response_completeness_result": "pass",
173-
"response_completeness_threshold": 3,
174-
"response_completeness_reason": "The response contains all major recommendations and explanations from the ground truth, with only a minor omission of the explicit dependency statement. It is thorough and actionable.",
175-
"overall_score": 0.0
176-
},
177149
{
178150
"testcase": "Python emitter issue with bulleted list TypeSpec doc string, and other",
179151
"expected": {

0 commit comments

Comments
 (0)