.NET: Python: Add dotnet integration test report to CI

[giles17]

Motivation and Context

Improve .NET integration test reliability and add visibility into test results across CI runs. This PR:

1. Adds a dotnet integration test report job (mirroring the existing Python report)
2. Adds retry logic ([RetryFact]) to flaky LLM-dependent integration tests to reduce spurious failures
3. Fixes minor CI issues (credential hygiene, test timeouts)

Description

Integration Test Report (dotnet-build-and-test.yml)

• Add --report-junit flag to integration test steps to generate JUnit XML output
• Add --results-directory ../IntegrationTestResults/ to centralize output (separate from unit test TRX results)
• Upload JUnit XML artifacts from each matrix leg (net10.0/ubuntu, net472/windows)
• Add new dotnet-integration-test-report job that aggregates results, generates a trend report, and posts to Job Summary
• Add persist-credentials: false to checkout step for security consistency

dotnet-test (net10.0/ubuntu) ──┐
                                ├──> dotnet-integration-test-report
dotnet-test (net472/windows) ──┘    (downloads JUnit XML, runs aggregate.py,
                                     posts to Job Summary, caches history)

The report job is not in the merge gate (dotnet-build-and-test-check doesn't depend on it) and only runs on non-PR events.

RetryFact for Flaky Integration Tests

• DurableTask (ConsoleAppSamplesValidation.cs, ExternalClientTests.cs, WorkflowConsoleAppSamplesValidation.cs): All LLM-dependent tests now use [RetryFact(2, 5000)] — retries once after 5s delay on transient LLM failures
• AzureFunctions (SamplesValidation.cs): Same retry pattern applied to all 7 active tests; LongRunningTools timeouts increased from 90s to 180s

Aggregate Script (python/scripts/integration_test_report/aggregate.py)

• Refactor XML file discovery to support both pytest (pytest.xml) and xunit (*.junit) layouts via _discover_xml_files()
• Handle dotnet artifact naming convention (dotnet-test-results-{framework}-{os})
• Fix node-id collision when the same test runs under multiple frameworks by qualifying keys with provider
• Generate per-framework tables for dotnet results
• Improve module extraction for dotnet C# classnames (recognizes IntegrationTests/UnitTests namespace segments)

Key Design Decisions

• JUnit XML via --report-junit instead of parsing TRX — xunit v3 supports native JUnit generation, allowing reuse of the existing Python report script
• Integration-only — unit tests run on different cadence (PRs vs merges); mixing would make trends incomparable
• Separate history stream — distinct cache key (dotnet-integration-report-history-) prevents dotnet/Python history from interleaving
• RetryFact over CI-level retry — per-test retry is faster and more targeted than re-running the entire job

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? No

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 90% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach

---

Automated review by giles17's agents

[Copilot]

Pull request overview

This PR adds CI visibility for .NET integration test outcomes by publishing JUnit XML from the existing dotnet-test matrix legs and reusing the existing Python trend-aggregation script to generate a Job Summary report with cached history.

Changes:

• Update the .NET integration test step to emit JUnit XML into a dedicated IntegrationTestResults/ directory and upload those XML files as per-matrix artifacts.
• Add a new dotnet-integration-test-report job that downloads the artifacts, aggregates them into a trend report, posts it to the GitHub Actions Job Summary, and caches history.
• Refactor python/scripts/flaky_report/aggregate.py to discover both pytest.xml and *.junit.xml, derive dotnet “provider” labels, and avoid nodeid collisions across providers.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
python/scripts/flaky_report/aggregate.py	Extends report discovery/parsing to support dotnet xUnit JUnit XML and multi-provider collision handling.
.github/workflows/dotnet-build-and-test.yml	Generates/uploads dotnet integration JUnit XML and adds a reporting job to aggregate and publish a trend report.

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 90% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach

---

Automated review by giles17's agents