Skip to content
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

Add check to not private builds to public channels #15041

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

remove comment

e4a7f3d
Select commit
Loading
Failed to load commit list.
Open

Add check to not private builds to public channels #15041

remove comment
e4a7f3d
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Nov 5, 2024 in 41m 31s

Build #20241105.11 had test failures

0 errors / 0 warnings

Details

Tests

  • Failed: 36 (0.42%)
  • Passed: 8,204 (95.64%)
  • Other: 338 (3.94%)
  • Total: 8,578

Annotations

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

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