Flaky test: ['Aspire.Hosting.Elasticsearch.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

dotnet / aspire

Tools, templates, and packages to accelerate building observable, production-ready apps

https://learn.microsoft.com/dotnet/aspire

MIT License

3.88k stars 469 forks source link

Flaky test: ['Aspire.Hosting.Elasticsearch.Tests' END OF WORK ITEM LOG: Command timed out, and was killed] #5821

Open davidfowl opened 1 month ago

davidfowl commented 1 month ago

Seems like we need to extend the timeout for elastic search tests. I can't tell which tests were running when it failed, the logs are pretty interleaved.

Trx:

Aspire.Hosting.Elasticsearch.Tests.zip

JamesNK commented 1 month ago

Another one: https://dev.azure.com/dnceng-public/public/_build/results?buildId=815343&view=ms.vss-test-web.build-test-results-tab&runId=21136180&resultId=101496&paneView=dotnet-dnceng.dnceng-anon-build-release-tasks.helix-anon-test-information-tab

JamesNK commented 1 month ago

In ASP.NET Core repo we often add DefaultTimeout() to every await in test files. That way you know exactly which test hung and at what link in the test. Adding DefaultTimeout everywhere is a pain though.

davidfowl commented 1 month ago

There’s usually also a dump captured (but it’s on Linux 😬)

radical commented 1 month ago

btw, the changes in https://github.com/dotnet/aspire/pull/5861/files#diff-9d5d1aacb93015b5071c24986affe471f501b7de959aefe1d1708a37724f30ea would be useful to get proper timeouts for anyone debugging this issue.