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.

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

Bring back properties until we re-bootstrap to a newer Arcade SDK #15330

Merged
merged 1 commit into from
Dec 12, 2024

Bring back properties back until we re-bootstrap to a newer Arcade

10aadb6
Select commit
Loading
Failed to load commit list.
Merged

Bring back properties until we re-bootstrap to a newer Arcade SDK #15330

Bring back properties back until we re-bootstrap to a newer Arcade
10aadb6
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Dec 12, 2024 in 35m 13s

Build #20241212.3 had test failures

Details

Tests

  • Failed: 36 (0.42%)
  • Passed: 8,224 (95.25%)
  • Other: 374 (4.33%)
  • Total: 8,634

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