Skip to content

Update version #16605

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

Closed
missymessa wants to merge 2 commits into from
+2 −2

Merge branch 'release/8.0' into missymessa-10068

9477eb6
Select commit
Loading
Failed to load commit list.
Closed

Update version #16605

Merge branch 'release/8.0' into missymessa-10068
9477eb6
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Mar 18, 2026 in 5h 33m 25s

Build #20260318.6 had test failures

0 errors / 4 warnings

Details

Tests

  • Failed: 36 (0.74%)
  • Passed: 4,614 (94.98%)
  • Other: 208 (4.28%)
  • Total: 4,858

Annotations

Check failure on line 1 in XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath 

Intentional Failure 🍕 
 
 	     
Expected: True
Actual:   False
Raw output 
   at XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath() in Class1.cs:line 1

Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRX.Fail2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporter.TRXTests.HelixReporter.TRX.Fail2 

                        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.TestMethod4() in UnitTest1.cs:line 26

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

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
View more details on Azure Pipelines