flaky test: Aspire.Hosting.Tests.DistributedApplicationTests.StartResourceForcesStart

[davidfowl]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=935714
Build error leg or test failing: Aspire.Hosting.Tests.DistributedApplicationTests.StartResourceForcesStart
Pull request: #7331

Error Message

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

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

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[davidfowl]

Assigning to you @JamesNK as this is a new test.

[davidfowl]

StopResourceAsync hangs and doesn't stop the resource, that's why this test failed. We should add more verbose logs in DcpExecutor and ApplicationOrchestrator.

[karolz-ms]

I will take a look as well

[karolz-ms]

From the logs I doubt this is caused by StopResourceAsync() hanging. Rather, the test timed out because it never got a notification from DCP that the "ServiceB" process exited. Because it actually didn't. Or rather DCP never got a result of a wait() call on the process ID, despite sending (successfully) SIGTERM followed by SIGKILL to it. I am not really sure why that might be the case.

[davidfowl]

@karolz-ms Another failure of this with DCP logs this time:

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=937572
Build error leg or test failing: Aspire.Hosting.Tests.DistributedApplicationTests.StartResourceForcesStart
Pull request: #7374

Error Message

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

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