Skip to content

Failing test: Aspire.Dashboard.Components.Tests.Pages.ConsoleLogsTests.ReadingLogs_ErrorDuringRead_SetStatusAndLog #12740

@radical

Description

@radical

Build Information

Build: https://github.com/dotnet/aspire/actions/runs/19120784532
Build error leg or test failing: Aspire.Dashboard.Components.Tests.Pages.ConsoleLogsTests.ReadingLogs_ErrorDuringRead_SetStatusAndLog
Pull request:

Error Message

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

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

Error Details

Bunit.Extensions.WaitForHelpers.WaitForFailedException : The state predicate did not pass before the timeout period passed.

If this test does not fail consistently, the reason may be that
the wait timeout is too short, and the runtime did not have enough
time to complete the necessary number of renders of the component under test.
This can happen on highly utilized or slower hardware, for example.

To determine if this is the cause, compare the check and render count(s) below
and see if they match what is expected. If they do not,
consider increasing the timeout, either at the individual
method call level, e.g. WaitForElement("div", TimeSpan.FromSeconds(15)),
or via the static TestContext.DefaultWaitTimeout property.

Check count: 1.
Component render count: 4.
Total render count across all components: 5.
Stack Trace
at Bunit.RenderedFragmentWaitForHelperExtensions.WaitForState(IRenderedFragmentBase renderedFragment, Func`1 statePredicate, Nullable`1 timeout) in /_/src/bunit.core/Extensions/WaitForHelpers/RenderedFragmentWaitForHelperExtensions.cs:line 32
   at Aspire.Dashboard.Components.Tests.Pages.ConsoleLogsTests.ReadingLogs_ErrorDuringRead_SetStatusAndLog() in /_/tests/Aspire.Dashboard.Components.Tests/Pages/ConsoleLogsTests.cs:line 379
--- End of stack trace from previous location ---

Report for Quarantined runs

Recent runs:

OS Last 100 runs
linux (0/100) No failures ✅
macos (0/100) No failures ✅
windows (0/100) No failures ✅

Summary

Last 10 runs Last 50 runs Last 100 runs Most Affected OS Failure Rate
0 0 0 N/A 0.0%

-- Updated on 1/13/2026 7:46:27 PM UTC

Metadata

Metadata

Assignees

Labels

flaky-testquarantined-testQuarantined tests that run only in the Outerloop Tests workflow

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions