Skip to content

[Evaluation] Prepare azure-ai-evaluation 1.18.6 release - #49074

Open
Ankit Singhal (singankit) wants to merge 2 commits into
mainfrom
singankit-evaluation-release-readiness
Open

Ankit Singhal (singankit) wants to merge 2 commits into
mainfrom
singankit-evaluation-release-readiness

Conversation

@singankit

Copy link
Copy Markdown
Contributor

Description

Prepare azure-ai-evaluation 1.18.6 for release following the package-specific release process.

Release tracking: https://dev.azure.com/azure-sdk/Release/_workitems/edit/35140/ — updated to In Release, version 1.18.6.

Release handoff

  • Human review and merge to main are required before running python - evaluation (7162) on main.
  • The preparation script successfully contacted APIView (HTTP 201) and reported that the API review for 1.18.6 is not approved; the package name is approved. Confirm the release build's revision under Build > Analyze > Create API Review.
  • The API surface differs from 1.18.5: evaluate adds aoai_output_items_page_size. Reviewers should confirm API approval and suitability of the existing patch version before release.
  • Explicit approval from Minsoo and approval of the publishing stage remain required. No release pipeline was queued and nothing was published during preparation.

Validation

  • Confirm-ChangeLogEntry -VersionString '1.18.6' -ForRelease $true passed.
  • git diff --check passed.
  • Changelog-only change; no runtime code changes.

All SDK Contribution checklist:

  • The pull request does not introduce breaking changes.
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message.

Testing Guidelines

  • Pull request includes test coverage for the included changes. Not applicable: release changelog only.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added the Evaluation Issues related to the client library for Azure AI Evaluation label Sep 18, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@singankit
Ankit Singhal (singankit) marked this pull request as ready for review September 18, 2026 05:13
Copilot AI balanced review requested due to automatic review settings September 18, 2026 05:13
@singankit
Ankit Singhal (singankit) requested a review from a team as a code owner September 18, 2026 05:13
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The new public feature requires a minor version bump rather than the proposed patch version.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Prepares azure-ai-evaluation for release by finalizing its changelog.

Changes:

  • Dates the release and documents AOAI pagination and retry behavior.
  • Removes empty changelog sections.
File summaries
File Description
sdk/evaluation/azure-ai-evaluation/CHANGELOG.md Finalizes release notes for the proposed version.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

# Release History

## 1.18.6 (Unreleased)
## 1.18.6 (2026-09-17)
@github-actions

Copy link
Copy Markdown
Contributor
[Pilot] PR Pipeline Failure Analysis

What failed

Build: 6853636python - pullrequest (FAILURE), job Build Test macoslatest_311
Package/path: sdk/evaluation/azure-ai-evaluation
Test: sdk.evaluation.azure-ai-evaluation.tests.unittests.test_evaluate.TestEvaluate.test_evaluate_korean_characters_result
File: tests/unittests/test_evaluate.py:1083

Relevant pipeline output
self = <test_evaluate.TestEvaluate object at 0x1128ed5d0>
questions_answers_korean_file = '/Users/runner/work/1/s/sdk/evaluation/azure-ai-evaluation/tests/unittests/data/questions_answers_korean.jsonl'

    def test_evaluate_korean_characters_result(self, questions_answers_korean_file):
        output_path = "eval_test_results_korean.jsonl"

        result = evaluate(
            data=questions_answers_korean_file,
            evaluators={"g": F1ScoreEvaluator()},
            output_path=output_path,
        )

        assert result is not None

        with open(questions_answers_korean_file, "r", encoding="utf-8") as f:
            first_line = f.readline()
            data_from_file = json.loads(first_line)

        assert result["rows"][0]["inputs.query"] == data_from_file["query"]

>       os.remove(output_path)
E       FileNotFoundError: [Errno 2] No such file or directory: 'eval_test_results_korean.jsonl'

tests/unittests/test_evaluate.py:1083: FileNotFoundError

Root cause

The evaluate() call did not write eval_test_results_korean.jsonl to the expected relative working directory on the macoslatest_311 runner, so the test's own cleanup step (os.remove(output_path)) raised FileNotFoundError. This is a test-cleanup/output-path failure category, not an AssertionError on evaluation content — the assertions above it appear to have passed, meaning evaluate() returned a result but the output file wasn't found at the relative path used for cleanup. This is platform-specific (only observed on macoslatest_311), consistent with a working-directory or file-flush timing difference rather than a logic bug in the evaluator itself.

This PR (singankit-evaluation-release-readiness) is changelog-only — it updates CHANGELOG.md and version metadata for release prep and makes no runtime code changes to evaluate() or any output-path handling. The failure is therefore not something this PR's diff caused, and cannot be fixed by editing this PR's changed file (CHANGELOG.md).

Recommended next steps

  • Re-run the macoslatest_311 pipeline job to rule out a transient/platform timing issue (e.g., delayed file flush before test cleanup).
  • If it fails again, investigate evaluate()'s output-path/working-directory handling for macOS runners in the package's live source (not reachable from this PR's diff), possibly related to the adaptive timeout retry / output-item paging behavior recently introduced in [Evaluation] Configure adaptive native AOAI output result page size #49034.
  • See https://aka.ms/ci-fix

Copilot detected the failing pipeline and generated the analysis above. To have it attempt a
fix automatically, reply with @copilot please fix the failing pipeline on this PR.

Generated by Pipeline Analysis Next Steps · auto · 62.4 AIC · ⌖ 7.03 AIC · ⊞ 8.7K ·

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Evaluation Issues related to the client library for Azure AI Evaluation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants