search

dotnet / aspire

Tools, templates, and packages to accelerate building observable, production-ready apps
https://learn.microsoft.com/dotnet/aspire
MIT License
3.93k stars 480 forks source link

Flaky playground tests due to `Failed to bind to address ` #6355

Open radical opened 1 month ago

radical commented 1 month ago

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=845546 Build error leg or test failing: Aspire.Playground.Tests.AppHostTests.Aspire.Playground.Tests.AppHostTests.TestEndpointsReturnOk Pull request: https://github.com/dotnet/aspire/pull/6235

Error Message

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

{
  "ErrorMessage": "",
  "ErrorPattern": "Failed to bind to address .*address already in use",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=845546 Error message validated: [Failed to bind to address .*address already in use] Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 10/17/2024 7:33:49 AM UTC

Report

Build Definition Test Pull Request
863093 dotnet/aspire Aspire.Playground.Tests.WorkItemExecution
855075 dotnet/aspire Aspire.Playground.Tests.AppHostTests.Aspire.Playground.Tests.AppHostTests.TestEndpointsReturnOk dotnet/aspire#6487

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 2
radical commented 1 month ago

The instances of this are likely because a previous projects are still running, so we should probably wait for dcp processes to disappear.