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