Skip to content

Failing test: Aspire.Hosting.Docker.Tests.DockerComposeTests.PushImageToRegistry_WithRemoteRegistry_PushesImage #13878

@radical

Description

@radical

Build Information

Build: https://github.com/dotnet/aspire/actions/runs/20947646510
Build error leg or test failing: Aspire.Hosting.Docker.Tests.DockerComposeTests.PushImageToRegistry_WithRemoteRegistry_PushesImage
Pull request:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "PushImageAsync should have been called for remote registry",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Error Details

Error Message: PushImageAsync should have been called for remote registry
Stack Trace:
at Aspire.Hosting.Docker.Tests.DockerComposeTests.PushImageToRegistry_WithRemoteRegistry_PushesImage() in D:\a\aspire\aspire\tests\Aspire.Hosting.Docker.Tests\DockerComposeTests.cs:line 677
--- End of stack trace from previous location ---

Report for Quarantined runs

Recent runs:

OS Last 100 runs
linux (0/100) No failures ✅
macos (0/100) No failures ✅
windows (0/100) No failures ✅

Summary

Last 7 days Last 14 days Last 30 days Most Affected OS Failure Rate
0 / 82 0 / 157 0 / 344 N/A 0.0%

-- Updated on 2/18/2026 6:18:48 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    failing-testflaky-testneeds-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersquarantined-testQuarantined tests that run only in the Outerloop Tests workflow

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions