[AI discovered CI] YAML config error: unexpected parameter 'useFullyQualifiedTestName' in .vsts-pr.yml

[github-actions]

Fork-only CI monitor evaluation; not a production tracking issue.

Build Information

• Build: 1521345
• Branch: refs/pull/55404/merge
• Pipeline: dotnet-sdk-public-ci (def 101, dnceng-public/public)
• Queued: 2026-07-22T11:09:40Z
• Phase: pipeline-validation
• Failure type: configuration-error
• Evidence sources: azure-validation
• Failure fingerprint: pipeline-validation|configuration-error|dotnet-sdk-public-ci|.vsts-pr.yml-line-<n>-col-<n>-unexpected-parameter-usefullyqualifiedtestname

Failure History

One occurrence recorded in the dossier. The build was zero-duration (YAML pre-flight rejection); no timeline or test results were produced. No related builds with the same mechanism are reported. Actionability is based on the deterministic configuration-error rule: one occurrence is sufficient when the diagnostic clearly identifies an SDK-owned YAML break.

Error Details

/.vsts-pr.yml (Line: 59, Col: 34): Unexpected parameter 'useFullyQualifiedTestName'

Build result: failed. Duration: effectively zero (pre-flight rejection). No test results available (404 from test runs API).

Root Cause Analysis

Observed: PR build 1521345 was rejected during YAML pipeline validation before any job ran. The AzDO pipeline pre-flight parser reported an unexpected parameter useFullyQualifiedTestName at .vsts-pr.yml line 59, column 34.

Assessment: A parameter named useFullyQualifiedTestName was passed to a step or template that does not declare it. This is an SDK-owned YAML change introduced in PR dotnet#55404 that introduced a parameter not accepted by the referenced template version. The build cannot proceed until the YAML is corrected or the template is updated to accept the parameter.

Confidence: High — the AzDO YAML validator produces a deterministic error with exact file, line, and column; the failure is entirely contained in the SDK-owned .vsts-pr.yml.

Alternatives / Unknowns: The template referenced at the call site may itself need updating to accept the new parameter (the fix may be in the template definition rather than the call site). The exact template path and version are not in the dossier.

Suggested Investigation

1. Next check: Inspect .vsts-pr.yml around line 59 in PR Enable fully qualified Helix test name reporting dotnet/sdk#55404. Identify the template step being called and whether it declares a useFullyQualifiedTestName parameter.
2. If the template does not declare the parameter, either remove the parameter from the call site or add it to the template definition.
3. Re-queue the PR build after the fix to confirm pre-flight validation passes.

Generated by 🕵️ CI Quality Investigator · 22.2 AIC · ⌖ 4.79 AIC · ⊞ 7.5K · ◷