Conversation
Publishing multiple disjoint per-assembly XUnit result files into a single ADO test run (mergeTestResults: true) makes the Publish Test Results task emit a 'TestResultConverter.ConvertResults : No matching test case result found on server' warning for every test in every file after the first -- tens of thousands of warnings per build (63k+ observed) -- and can abort with 'TestCaseTitle must be specified', silently dropping a whole assembly's results. Publish each assembly's XUnit file as its own run instead. Applied to the shared batched-test-steps template and the three explicit PublishTestResults tasks in azure-pipelines-PR.yml. The official azure-pipelines.yml already omits mergeTestResults (defaults to false). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee9b5f2a-94a7-4b63-ad52-6602d2a0bda6
github-actions
Bot
added
the
AI-Tooling-Check-Bypassed
Split Linux CoreCLR tests into the existing two batches to reduce test-process memory pressure after the exit-137 termination. Keep complete coverage and give each batch distinct test-run and artifact names. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…tresultsconverter-warning Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> # Conflicts: # azure-pipelines-PR.yml
…tresultsconverter-warning
abonie
reviewed
Sep 22, 2026
| # found on server" warning for every test in every file after the first (tens of thousands | ||
| # of warnings per build), and can abort with "TestCaseTitle must be specified", silently | ||
| # dropping a whole assembly's results. | ||
| mergeTestResults: false |
Member
There was a problem hiding this comment.
This still drops assembly results in build 1605407's Linux Batch1 run: the publisher sends 117 results to run 44355152, then tries to publish the 6,175 component results to that same run and aborts with TestCaseTitle must be specified…. Setting mergeTestResults: false hasn't isolated the runs here. We need to verify that each XML actually produces a separate, complete run before calling this fixed.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mergeTestResults: truemerges the disjoint per-assembly XUnit files from one job into a single Azure DevOps test run. The publisher then emits aTestResultConverter.ConvertResults : No matching test case result found on serverwarning for every test in every file after the first — 63k+ warnings in a single build — and intermittently aborts withTestCaseTitle must be specified, which silently drops a whole assembly's results. Publishing each file as its own run removes both.