Skip to content

Replace external PublishSymbols task with SymbolUploadHelper-based task (WI 10148/10149) #16691

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

Open
missymessa wants to merge 8 commits into
base: main
Choose a base branch
from
+354 −26

Merge branch 'main' into missymessa-10148-10149

e8f4a58
Select commit
Loading
Failed to load commit list.
Open

Replace external PublishSymbols task with SymbolUploadHelper-based task (WI 10148/10149) #16691

Merge branch 'main' into missymessa-10148-10149
e8f4a58
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Apr 28, 2026 in 51m 34s

Build #20260427.16 had test failures

0 errors / 3 warnings

Details

Tests

  • Failed: 48 (1.27%)
  • Passed: 3,342 (88.23%)
  • Other: 398 (10.51%)
  • Total: 3,788

Annotations

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 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.Fail1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

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