Failing test: Aspire.Hosting.Tests.Dcp.DcpExecutorTests.PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde

[radical]

Build Information

Build: https://github.com/dotnet/aspire/actions/runs/18602193053
Build error leg or test failing: Aspire.Hosting.Tests.Dcp.DcpExecutorTests.PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde
Pull request:

Error Message

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

{
  "ErrorMessage": "",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Assert.Equal() Failure: Values differ
Expected: 2
Actual:   1   at Aspire.Hosting.Tests.Dcp.DcpExecutorTests.PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde() in /Users/runner/work/aspire/aspire/tests/Aspire.Hosting.Tests/Dcp/DcpExecutorTests.cs:line 1577
--- End of stack trace from previous location ---

Last 10 failures:

Run date	Build Type	Test Name	OS
oct 27 4 pm	danegsta/reworkCertConfigApi@fa8a710	PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde	windows
oct 27 4 pm	danegsta/reworkCertConfigApi@fa8a710	PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde	macos
oct 27 4 pm	danegsta/reworkCertConfigApi@fa8a710	PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde	linux
oct 27 3 pm	main@1f493e6	PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde	macos
oct 27 2 pm	azurecloud@b859273	PlainExecutable_ExtensionMode_SupportedDebugMode_RunsInIde	macos

Summary

Last 24 hrs	Last 7 days	Last 30 days	Most Affected OS	Failure Rate
0	5 (0 PRs, 5 rolling)	5 (0 PRs, 5 rolling)	macos (60%)	0.0%

-- Updated on 10/31/2025 7:09:12 AM UTC

[karolz-ms]

The assert that is failing is in the following test code:

 await Task.Delay(2000);
 // Assert
 var dcpExes = kubernetesService.CreatedResources.OfType<Executable>().ToList();
 Assert.Equal(2, dcpExes.Count);

The fixed delay of 2 seconds is both too small and is the source of test instability. Instead, I suggest probing for correct number of created Executables (2) with exponential backoff and long timeout, e.g. 30 seconds. This will reduce the flakiness AND improve happy path execution time.