[✨ Triage] dotnet/aspire#12409 by radical - Failing test: Aspire.Dashboard.Tests.Integration.StartupTests.LogOutput_ ...

[MihuBot]

Triage for microsoft/aspire#12409.
Repo filter: area-dashboard issues.
MihuBot version: fe265e.
Ping MihaZupan for any issues.

This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.

Tool logs

dotnet/aspire#12409: Failing test: Aspire.Dashboard.Tests.Integration.StartupTests.LogOutput_LocalhostAddress_LocalhostInLogOutput by radical
[Tool] Searching for LogOutput_LocalhostAddress_LocalhostInLogOutput, Assert.Collection() Failure, dashboard is configured with a shared endpoint for browser access and the OTLP service, Now listening on: https://localhost, StartupTests (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 40 issues, 79 comments (39985 ms)

Here are related issues, PRs, and discussions relevant to issue #12409 ("Failing test: Aspire.Dashboard.Tests.Integration.StartupTests.LogOutput_LocalhostAddress_LocalhostInLogOutput"):

---

1. Directly Related Test Failures and Fixes

• PR #3473 (April 2024) - Fix flaky LogOutput_LocalhostAddress_LocalhostInLogOutput

  • Link
  • This PR addressed flakiness in the same test by ensuring the sink was recreated on each retry. If the current failure is intermittent, this previous fix may be relevant, but if the error pattern has changed, further investigation is needed.

• PR #3045 (March 2024) - Support configuring dashboard with one endpoint for browser and OTLP

  • Link
  • This PR changed dashboard behavior when a single endpoint is used for both browser and OTLP access. It logs a warning if the endpoint is not secured with TLS, which matches the warning message seen in your test failure. This change may have altered log output order/content, affecting test expectations.

---

2. Recent Changes to Endpoint and Log Output Handling

• *PR #12466 (October 2025) - Make .localhost resource endpoint URLs the primary endpoint URL

  • Link
  • This PR, merged very recently, changes how localhost endpoints are displayed and prioritized. If your test expects a specific log output regarding localhost addresses, this change could affect the test.

• Issue #1635 (January 2024) - Endpoint url is http://127.0.0.1:xxx instead of http://localhost:xxx in the dashboard

  • Link
  • Discusses the nuances of localhost vs. 127.0.0.1 in endpoint reporting. The dashboard may display one or the other depending on binding and resolution logic, which can affect log output and test assertions.

---

3. Dashboard Endpoint Configuration and Log Output

• PR #3045 (March 2024) - Support configuring dashboard with one endpoint for browser and OTLP

  • Link
  • As above, this PR introduced a warning log when the dashboard is configured with a shared endpoint that does not use TLS. Your test failure shows this warning appearing in the log output, possibly in a position not expected by the test.

• Issue #2756 (March 2024) - Aspire Dashboard HTTPS and SINGLE PORT hosting of both OTLP and Blazor app

  • Link
  • User describes hosting both dashboard and OTLP on a single port, with HTTPS. This scenario is now supported and may affect log output order/content.

---

4. General Log Output and Assertion Issues

• Issue #5184 (August 2024) - Test failure on CI : Aspire.Hosting.MongoDB.Tests.MongoDbFunctionalTests.VerifyWithInitBindMount

  • Link
  • Another test using Assert.Collection() failed due to unexpected log output. While not directly related, it shows that log output order/content can be a source of test flakiness.

• PR #8976 (April 2025) - xUnit2031 Do not use Where clause with Assert.Single

  • Link
  • Refactors tests to avoid using Where with Assert.Single, which can cause assertion failures if log output changes.

---

5. Recent Changes to Dashboard Endpoint Binding and Proxying

• PR #10576 (July 2025) - Use proxied endpoints for aspire dashboard
  • Link
  • Dashboard endpoints now bind to random ports via DCP proxies, which may affect log output and the ports shown in logs.

---

6. Discussions and Comments on Log Output and Endpoint Display

• Issue #9784 (June 2025) - Dashboard used wrong ports for the app
  • Link
  • Reports dashboard displaying incorrect ports due to proxy binding issues. Log output may not match expectations if ports are reassigned.

---

7. Summary of Likely Cause

• The test failure is due to an unexpected log message ("The dashboard is configured with a shared endpoint for browser access and the OTLP service. The endpoint doesn't use TLS so browser access is only possible via a TLS terminating proxy.") appearing in the log output, possibly in a position not expected by the test.
• This warning was introduced in PR #3045 and is logged when the dashboard is configured with a shared endpoint without TLS.
• Recent changes (PR #12466) may also affect how localhost endpoints are displayed and prioritized in logs.
• The test may need to be updated to account for the new log output order/content, or the dashboard's log output may need to be adjusted to restore previous behavior.

---

Recommendations

• Review PR #3045 and PR #12466 for changes to log output and endpoint display logic.
• Update the test to expect the warning message if the dashboard is configured with a shared endpoint without TLS.
• If the test is meant to verify the presence of "Now listening on: https://localhost:..." in the log output, ensure it accounts for any preceding warning messages.
• Consider whether the log output order is deterministic or if the test should be made more flexible.

---

If you need a deeper dive into any specific PR or issue, let me know!