Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Bug]: Timeout — Resources not ready #5260

Copy link
Copy link

Description

@Zodt
Issue body actions

Description

After upgrading the Aspire.Hosting.AppHost version from 13.1.3 to 13.2.0 (#5232), an error started to occur.

Expected Behavior

Pass integration test

Actual Behavior

See Error Output / Stack Trace

Steps to Reproduce

  1. Add Aspire.Host project with Aspire.Hosting.AppHost [v13.2.0] to the solution.
  2. Add Integration tests project by TUnit.Aspire [v1.21.30]
  3. Add some integration test
  4. Run integration tests

TUnit Version

1.21.30

.NET Version

.NET10

Operating System

Windows

IDE / Test Runner

JetBrains Rider / CLI

Error Output / Stack Trace

[Timeout] Resources not ready: ['resource-name-rebuilder']. Resources ready: ['resource-name', 'object-storage', 'cache']

--- resource-name-rebuilder logs ---
  (no logs available)
   at TUnit.Aspire.AspireFixture`1.WaitForResourcesWithFailFastAsync(DistributedApplication app, ResourceNotificationService notificationService, List`1 resourceNames, Boolean waitForHealthy, CancellationToken cancellationToken)
   at TUnit.Aspire.AspireFixture`1.WaitForResourcesAsync(DistributedApplication app, CancellationToken cancellationToken)
   at TUnit.Aspire.AspireFixture`1.InitializeAsync()
   at TUnit.Core.ObjectInitializer.InitializeCoreAsync(Object obj, IAsyncInitializer asyncInitializer, CancellationToken cancellationToken)
   at TUnit.Engine.Services.ObjectLifecycleService.InitializeObjectWithNestedAsync(Object obj, CancellationToken cancellationToken)
   at TUnit.Engine.Services.ObjectLifecycleService.InitializeTrackedObjectsAsync(TestContext testContext, CancellationToken cancellationToken)
   at TUnit.Engine.TestInitializer.InitializeTestObjectsAsync(AbstractExecutableTest test, CancellationToken cancellationToken)
   at TUnit.Engine.TestExecutor.ExecuteAsync(AbstractExecutableTest executableTest, TestInitializer testInitializer, CancellationToken cancellationToken, Nullable`1 testTimeout)
   at TUnit.Engine.TestExecutor.ExecuteAsync(AbstractExecutableTest executableTest, TestInitializer testInitializer, CancellationToken cancellationToken, Nullable`1 testTimeout)
   at TUnit.Engine.Services.TestExecution.TestCoordinator.ExecuteTestLifecycleAsync(AbstractExecutableTest test, CancellationToken cancellationToken)
   at TUnit.Engine.Services.TestExecution.TestCoordinator.ExecuteTestLifecycleAsync(AbstractExecutableTest test, CancellationToken cancellationToken)
   at TUnit.Engine.Services.TestExecution.RetryHelper.ExecuteWithRetry(TestContext testContext, Func`1 action)
   at TUnit.Engine.Services.TestExecution.RetryHelper.ExecuteWithRetry(TestContext testContext, Func`1 action)
   at TUnit.Engine.Services.TestExecution.TestCoordinator.ExecuteTestInternalAsync(AbstractExecutableTest test, CancellationToken cancellationToken)

Additional Context

<IsAotCompatible>true</IsAotCompatible>
<EnableTrimAnalyzer>true</EnableTrimAnalyzer>

IDE-Specific Issue?

  • I've confirmed this issue occurs when running via dotnet test or dotnet run, not just in my IDE
Reactions are currently unavailable

Metadata

Metadata

Labels

bugSomething isn't workingSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

Morty Proxy This is a proxified and sanitized view of the page, visit original site.