Skip to content

More powerful virtual test server for unit tests #2158

More powerful virtual test server for unit tests

More powerful virtual test server for unit tests #2158

Triggered via pull request February 27, 2026 13:06
Status Failure
Total duration 9m 12s
Artifacts

CI.yml

on: pull_request
StackExchange.Redis (Ubuntu)
2m 54s
StackExchange.Redis (Ubuntu)
StackExchange.Redis (Windows Server 2022)
9m 5s
StackExchange.Redis (Windows Server 2022)
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
StackExchange.Redis (Windows Server 2022)
Failed test were found and 'fail-on-error' option is set to true
StackExchange.Redis (Windows Server 2022)
Process completed with exit code 1.
MovedUnitTests.KeyMigrationFollowed(allowFollowRedirects: True) (RESP2): /_/tests/StackExchange.Redis.Tests/MovedUnitTests.cs#L50
StackExchange.Redis.RedisTimeoutException : The message timed out in the backlog attempting to send because no connection became available, command=GET, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Idle, last-in: 16, cur-in: 0, sync-ops: 0, async-ops: 4, serverEndpoint: 127.0.0.1:6380, conn-sec: 15.01, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: runnervmh5pn9(SE.Redis-v2.11.26.1291), PerfCounterHelperkeyHashSlot: 15004, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=1,Free=32766,Min=4,Max=32767), POOL: (Threads=6,QueuedItems=0,CompletedItems=112488,Timers=15), v: 2.11.26.1291 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
MovedUnitTests.KeyMigrationFollowed(allowFollowRedirects: False) (RESP2): /_/tests/StackExchange.Redis.Tests/MovedUnitTests.cs#L50
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: ReadAsync, ws: Idle, last-in: 16, cur-in: 0, sync-ops: 0, async-ops: 2, serverEndpoint: 127.0.0.1:6379, conn-sec: 15.05, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: runnervmh5pn9(SE.Redis-v2.11.26.1291), PerfCounterHelperkeyHashSlot: 15004, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=2,Free=32765,Min=4,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=112365,Timers=15), v: 2.11.26.1291 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
StackExchange.Redis (Windows Server 2022)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L5ehaQAAAAAAUSTmZD5DSbnfLauto/zcREVOMzAxMDAwMTA1MDIzAEVkZ2U=
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400