Skip to content

[release/9.0] Update dependencies from dotnet/xharness #16685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dotnet-maestro merged 2 commits into from
Apr 20, 2026
+3 −3

Update dependencies from https://github.com/dotnet/xharness build 202…

e4ab5d6
Select commit
Loading
Failed to load commit list.
Merged

[release/9.0] Update dependencies from dotnet/xharness #16685

Update dependencies from https://github.com/dotnet/xharness build 202…
e4ab5d6
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Apr 20, 2026 in 48m 30s

Build #20260419.2 had test failures

0 errors / 6 warnings

Details

Tests

  • Failed: 36 (0.35%)
  • Passed: 9,798 (96.05%)
  • Other: 367 (3.60%)
  • Total: 10,201

Annotations

Check failure on line 1 in HelixReporterTests.failure1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure1 

Intentional Failure
Raw output 
            This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.

Check failure on line 1 in HelixReporterTests.failure2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure2 

Intentional Failure
Raw output 
            This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.

Check failure on line 1 in tests.UnitTest2.ExpectedFailureTheoryTest

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

tests.UnitTest2.ExpectedFailureTheoryTest 

Test failed

Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1 

                        This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
Raw output 
   at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13
View more details on Azure Pipelines