Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing test Aspire.Hosting.Redis.Tests.RedisFunctionalTests.WithDataVolumeShouldPersistStateBetweenUsages #4863

Closed
radical opened this issue Jul 11, 2024 · 3 comments
Labels
area-integrations Issues pertaining to Aspire Integrations packages blocking-clean-ci Blocking a green CI redis Issues related to redis integrations testing ☑️

Comments

@radical
Copy link
Member

radical commented Jul 11, 2024

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=737846

  Failed Aspire.Hosting.Redis.Tests.RedisFunctionalTests.WithDataVolumeShouldPersistStateBetweenUsages [41 s]
  Error Message:

StackExchange.Redis.RedisTimeoutException : The message timed out in the backlog attempting to send because no connection became available, command=SET, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: ComputeResult, ws: Idle, in: 0, in-pipe: 1214, out-pipe: 0, last-in: 0, cur-in: 23, sync-ops: 0, async-ops: 1, serverEndpoint: localhost:33901, conn-sec: 10.3, aoc: 0, mc: 1/1/0, mgr: 9 of 10 available, clientName: bb829516c000000(SE.Redis-v2.8.0.27420), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=3,Free=32764,Min=4,Max=32767), POOL: (Threads=7,QueuedItems=4,CompletedItems=802,Timers=7), v: 2.8.0.27420 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

  Stack Trace:
     at Aspire.Hosting.Redis.Tests.RedisFunctionalTests.WithDataVolumeShouldPersistStateBetweenUsages() in /_/tests/Aspire.Hosting.Redis.Tests/RedisFunctionalTests.cs:line 87
--- End of stack trace from previous location ---

cc @sebastienros @eerhardt

Error Message

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

{
  "ErrorMessage": "RedisTimeoutException : The message timed out in the backlog attempting to send because no connection became available",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=737846
Error message validated: [RedisTimeoutException : The message timed out in the backlog attempting to send because no connection became available]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/15/2024 10:21:39 PM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication label Jul 11, 2024
@eerhardt
Copy link
Member

Do we know why the connection never became available? Did DCP fail somewhere?

@radical
Copy link
Member Author

radical commented Jul 11, 2024

This is from the log file - https://gist.github.com/radical/783aa3a0f77ff67eb41eb541ad57f5db .

@davidfowl davidfowl added area-integrations Issues pertaining to Aspire Integrations packages redis Issues related to redis integrations and removed area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication labels Sep 7, 2024
@radical
Copy link
Member Author

radical commented Sep 19, 2024

Closing this as it has not been hit in at least a month. And doesn't look actionable as-is.

@radical radical closed this as completed Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-integrations Issues pertaining to Aspire Integrations packages blocking-clean-ci Blocking a green CI redis Issues related to redis integrations testing ☑️
Projects
None yet
Development

No branches or pull requests

3 participants