Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-18_14_20_21.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout performing PING (400ms), next: PING, inst: 14, qu: 0, qs: 1, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 7, in-pipe: 0, out-pipe: 0, last-in: 414, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: 0.58, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: pkrvmq0rgcvqdmg(SE.Redis-v2.8.56.24632), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=5,Free=32762,Min=4,Max=32767), POOL: (Threads=5,QueuedItems=24,CompletedItems=250,Timers=43), v: 2.8.56.24632 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-18_14_20_21.trx Error: StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (400ms) - Last Connection Exception: UnableToConnect on 127.0.0.1:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.56.24632, command=PING, timeout: 400, inst: 0, qu: 1, qs: 0, aw: False, bw: Inactive, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: pkrvmq0rgcvqdmg(SE.Redis-v2.8.56.24632), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=8,Free=32759,Min=4,Max=32767), POOL: (Threads=27,QueuedItems=20,CompletedItems=1542,Timers=57), v: 2.8.56.24632 (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.RedisConnectionException : UnableToConnect on 127.0.0.1:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.56.24632

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-18_14_20_21.trx Error: StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code. ConnectTimeout

Failed test were found and 'fail-on-error' option is set to true

Process completed with exit code 1.

StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (400ms) - Last Connection Exception: UnableToConnect on 127.0.0.1:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.56.24632, command=PING, timeout: 400, inst: 0, qu: 1, qs: 0, aw: False, bw: Inactive, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: pkrvmq0rgcvqdmg(SE.Redis-v2.8.56.24632), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=8,Free=32759,Min=4,Max=32767), POOL: (Threads=27,QueuedItems=20,CompletedItems=1542,Timers=57), v: 2.8.56.24632 (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.RedisConnectionException : UnableToConnect on 127.0.0.1:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.56.24632

StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code. ConnectTimeout

StackExchange.Redis.RedisTimeoutException : Timeout performing PING (400ms), next: PING, inst: 14, qu: 0, qs: 1, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 7, in-pipe: 0, out-pipe: 0, last-in: 414, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: 0.58, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: pkrvmq0rgcvqdmg(SE.Redis-v2.8.56.24632), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=5,Free=32762,Min=4,Max=32767), POOL: (Threads=5,QueuedItems=24,CompletedItems=250,Timers=43), v: 2.8.56.24632 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-18_14_22_43.trx test-results/runneradmin_runnervm51nrn_2025-07-18_14_22_43.trx Error: StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-18_14_22_46.trx test-results/runneradmin_runnervm51nrn_2025-07-18_14_22_46.trx Error: StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

Failed test were found and 'fail-on-error' option is set to true

Process completed with exit code 1.

StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.

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>0sld6aAAAAABYNwOACn2GT6AFEHl8Sa0nQlkzRURHRTAxMTUARWRnZQ==