Skip to content

eng/common: detect FreeBSD/powerpc64le#17062

Open
pkubaj wants to merge 1 commit into
dotnet:mainfrom
pkubaj:ppc64le-freebsd-eng-common
Open

eng/common: detect FreeBSD/powerpc64le#17062
pkubaj wants to merge 1 commit into
dotnet:mainfrom
pkubaj:ppc64le-freebsd-eng-common

eng/common: detect FreeBSD/powerpc64le

f049c53
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Jun 30, 2026 in 25m 17s

Build #20260630.1 had test failures

Details

Tests

  • Failed: 48 (1.11%)
  • Passed: 3,898 (90.06%)
  • Other: 382 (8.83%)
  • Total: 4,328

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 🍕 \r \n \t \a \b \v \f \0\r\nExpected: True\r\nActual:   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

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

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

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