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

[automated] Merge branch 'release/8.0.1xx' => 'release/8.0.3xx' #43409

Closed

[automated] Merge branch 'release/6.0.4xx' => 'release/8.0.1xx' (#43400)

843e6e5
Select commit
Loading
Failed to load commit list.
Closed

[automated] Merge branch 'release/8.0.1xx' => 'release/8.0.3xx' #43409

[automated] Merge branch 'release/6.0.4xx' => 'release/8.0.1xx' (#43400)
843e6e5
Select commit
Loading
Failed to load commit list.
Azure Pipelines / dotnet-sdk-public-ci failed Sep 13, 2024 in 8m 40s

Build #20240913.5 had test failures

Details

Tests

  • Failed: 1 (0.01%)
  • Passed: 14,763 (93.38%)
  • Other: 1,046 (6.62%)
  • Total: 15,810

Annotations

Check failure on line 21 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-sdk-public-ci

Build log #L21

PowerShell exited with code '1'.

Check failure on line 9 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-sdk-public-ci

Build log #L9

Error: Not found SourceFolder: /Users/runner/work/1/s/artifacts

Check failure on line 42 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-sdk-public-ci

Build log #L42

Git fetch failed with exit code: 128

Check failure on line 9 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-sdk-public-ci

Build log #L9

Error: Not found SourceFolder: D:\a\_work\1\s\artifacts

Check failure on line 1 in dotnet-watch.Tests.dll.2.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-sdk-public-ci

dotnet-watch.Tests.dll.2.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.