[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/microsoft/testfx

• Subscription: 5e12033c-5337-464b-b504-9ec86a355360
• Build: 20260919.1 (332898)
• Date Produced: September 20, 2026 4:37:07 AM UTC
• Commit: f0fe5a89980d2b29daeb3c949c08d7f61b9cf939
• Branch: main

• Dependency Updates:
  • From 2.4.0-preview.26429.4 to 2.5.0-preview.26469.1
    • Microsoft.Testing.Platform
  • From 4.4.0-preview.26429.4 to 4.5.0-preview.26469.1
    • MSTest
    • MSTest.Sdk

[azure-pipelines]

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

[github-actions]

🔍 Build Failure Analysis — incomplete (binlog-mcp server unavailable)

The Azure DevOps build [1595273]((dev.azure.com/redacted) (dotnet-sdk-public-ci) failed, but this run's binlog-mcp server became unresponsive partway through analysis:

• binlog_errors succeeded quickly on the first two legs queried — 10_0_Windows_x64 and 4_0_Linux_x64 both reported zero errors.
• Every call after that (across the remaining 18 legs, plus even the trivial binlog_capabilities health check) timed out after 60s with context deadline exceeded, including after an explicit server-reset attempt.

As a result, no reliable root-cause analysis could be produced for this build. The following legs were never successfully checked:

10_1_Windows_x64, 10_2_Windows_x64, 1_0_Linux_arm64_AOT, 2_0_Linux_arm64, 3_0_Linux_x64_AOT, 3_1_Linux_x64_AOT, 4_1_Linux_x64, 4_2_Linux_x64, 5_0_Mac_arm64_AOT, 5_1_Mac_arm64_AOT, 6_0_Mac_arm64, 6_1_Mac_arm64, 6_2_Mac_arm64, 7_0_Windows_arm64_AOT, 8_0_Windows_x64_AOT, 8_1_Windows_x64_AOT, 9_0_Windows_x64_FullFramework, 9_1_Windows_x64_FullFramework

Please check the [Azure DevOps build]((dev.azure.com/redacted) directly for the authoritative failure logs, or re-trigger this analysis workflow once the binlog-mcp service has recovered.

---

_{🤖 Generated by the Build Failure Analysis workflow · commit 37ec2a6}

🤖 Automated content by GitHub Copilot. Generated by the Build Failure Analysis workflow. · auto · 91.9 AIC · ⌖ 1.84 AIC · ⊞ 7.2K · [◷]( · ◷)

[Evangelink]

I need some fixes on testfx

[joeloff]

I need some fixes on testfx

Like an additional flow, because this is the update from testfx?

[Evangelink]

I need some fixes on testfx

Like an additional flow, because this is the update from testfx?

Yes sorry! I had a bug on a new analyzer introduced that suggests [OSCondition] attribute based on [(Un)SupportedPlatform] one (I forgot to consider the -XXX, like in windows-xxx). It's now fixed and PR is updated.

[nagilson]

/azp run

Note

This retry was requested by GitHub Copilot during build-duty triage because product CI passed but Build Insights remained failed.

[azure-pipelines]

Command 'run

' is not supported by Azure Pipelines.

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[nagilson]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
3 pipeline(s) were filtered out due to trigger conditions.