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

Jump to bottom

Update Versions.Details.xml #14093

Merged
merged 2 commits into from
Oct 9, 2023

Update Version.Details.xml

5773851
Select commit
Loading
Failed to load commit list.
Merged

Update Versions.Details.xml #14093

Update Version.Details.xml
5773851
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-ci succeeded Oct 9, 2023 in 27m 32s

Build #20231008.7 had test failures

1 errors / 1 warnings

Details

Tests

  • Failed: 56 (0.77%)
  • Passed: 6,895 (95.33%)
  • Other: 282 (3.90%)
  • Total: 7,233

Annotations

Check failure on line 31 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-ci

Build log #L31 

Artifact Logs_Test_Linux_Debug_Helix already exists for build 431335.

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-ci

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 HelixReporter.TRXTests.HelixReporter.TRX.Fail2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-ci

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

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

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