Ankit Jain
Ankit Jain
The output from the app: ``` [2024-08-09T19:27:52] Aspire.Hosting.DistributedApplication Information: Aspire version: 8.1.1-ci [2024-08-09T19:27:52] Aspire.Hosting.DistributedApplication Information: Distributed application starting. [2024-08-09T19:27:52] Aspire.Hosting.DistributedApplication Information: Application host directory is: /mnt/vss/_work/1/s/tests/Aspire.Hosting.Tests [2024-08-09T19:27:52] Aspire.Hosting.Dcp.DcpHostService Information: Starting...
@mitchdenny should this be closed?
This hasn't been hit recently, and doesn't seem to be actionable. Closing. Please re-open if needed.
The issue was incorrectly closed. It was referenced in https://github.com/dotnet/aspire/pull/8801, and the commit was this test was reverted but the PR description still had the link.
This one seems to be part of a crashing Aspire.Hosting.Tests run where the single test times out after 10minutes.
I re-enabled this test after it did not fail for >100 runs, but then it failed on a PR. I think the issue here might be that a previous instance...
I think the CWD should be set before starting the apphost, so it has the same-ish environment as when using `dotnet run`. Does this make sense - https://github.com/dotnet/aspire/pull/5220 ?
We avoided changing the CWD for the process as it might cause issues for tests running in parallel. see [this](https://github.com/dotnet/aspire/pull/5220#discussion_r1709814032). The issue was fixed in https://github.com/dotnet/aspire/pull/5220 .
`BuildAndRunStarterTemplateBuiltInTest.BuildAndRunStarterTemplateBuiltInTest_Test("xunit.net")` runs test from the `xunit` test in the `aspire-starter` template. And that test is expected to fail but the `dotnet test` process is expected to return exit code `0`....