[CI] Use the local test report generator for Outerloop workflow

[Copilot]

This PR updates the Outerloop workflow to use the tools/GenerateTestSummary tool for generating test reports, aligning it with how test reporting is done in other workflows.

Changes made

• Added GenerateTestSummary tool call to individual test jobs in the Outerloop workflow, providing consistent per-test reporting
• Set up environment variables for running the dotnet script based on OS platform
• Replaced custom PowerShell script in the final results job with the GenerateTestSummary tool
• Added logic to organize test results by OS so that the summary generator can properly categorize them

Benefits

• Consistent test reporting format across all workflows
• Simplified maintenance by leveraging the same reporting tool everywhere
• Better alignment with the existing test summary generation pattern
• Reduced code duplication by removing custom parsing and report generation scripts

Fixes #9438.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[radical]

Can you trigger the Outerloop tests workflow to validate the changes here?

[radical]

We need to validate the case where one of the test job has a test failure. For that can you do the following:

1. Modify one of the quarantined tests to add a bug so the test fails
2. Then trigger the outerloop workflow so the changes here can be validated.

[radical]

Try that again

[radical]

@copilot We need to validate the case where one of the test job has a test failure. For that can you do the following:

Modify one of the quarantined tests to add a bug so the test fails
Then trigger the outerloop workflow so the changes here can be validated.

[Copilot]

@copilot We need to validate the case where one of the test job has a test failure. For that can you do the following:

Modify one of the quarantined tests to add a bug so the test fails
...

I've modified the YarpFunctionalTests.cs file to introduce a deliberate test failure. The test now expects a BadRequest status code instead of OK for the HTTP response, which will cause it to fail. The test is already quarantined and marked with the [QuarantinedTest] attribute, so it won't cause the main workflow to fail. This change will help validate that the test summary generator correctly identifies and reports failures in quarantined tests. The change is in commit 827cc3a.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• dnceng.pkgs.visualstudio.com
  • Triggering command: /home/REDACTED/work/aspire/aspire/.dotnet/dotnet build tests/Aspire.Hosting.Yarp.Tests/Aspire.Hosting.Yarp.Tests.csproj (dns block)
• pkgs.dev.azure.com
  • Triggering command: /home/REDACTED/work/aspire/aspire/.dotnet/dotnet build tests/Aspire.Hosting.Yarp.Tests/Aspire.Hosting.Yarp.Tests.csproj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[radical]

This is working well. You can drop the artificial test failure now, and we can take this PR out of draft.

[Copilot]

This is working well. You can drop the artificial test failure now, and we can take this PR out of draft.

I've removed the artificial test failure from YarpFunctionalTests.cs that was added for validation purposes. The test now correctly expects an OK status code again. This change is in commit 430266a.

[Copilot]

Pull Request Overview

This PR updates the Outerloop workflow to leverage the GenerateTestSummary tool for consistent test reporting. Key changes include adding OS-specific environment variable setup for the dotnet script, replacing a custom PowerShell processing block with a direct tool invocation, and reorganizing test result files by OS.

[radical]

@joperezr @danmoseley this is ready for merging.