Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout performing GET (5000ms), next: MULTI, inst: 4, qu: 0, qs: 42, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 3789, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, sync-ops: 742, async-ops: 313, serverEndpoint: 127.0.0.1:6379, conn-sec: 17.24, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: IncrDecrFloatingPointAsync, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=22,Free=32745,Min=4,Max=32767), POOL: (Threads=31,QueuedItems=155,CompletedItems=2823,Timers=37), v: 2.8.61.44828 (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-19_13_32_46.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout performing GET (5000ms), next: MULTI, inst: 660, qu: 0, qs: 42, aw: True, bw: SpinningDown, rs: ReadAsync, ws: Flushed, in: 555, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, sync-ops: 726, async-ops: 305, serverEndpoint: 127.0.0.1:6379, conn-sec: 12.24, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: IncrDecrFloatingPointAsync, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=17,Free=32750,Min=4,Max=32767), POOL: (Threads=31,QueuedItems=105,CompletedItems=2699,Timers=36), v: 2.8.61.44828 (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-19_13_32_46.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=1KiB, inbound=0KiB, 5001ms elapsed, timeout is 5000ms), command=SET, next: MULTI, inst: 0, qu: 6, qs: 42, aw: True, bw: CheckingForTimeoutComplete, rs: ReadAsync, ws: Flushed, in: 555, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, sync-ops: 731, async-ops: 306, serverEndpoint: 127.0.0.1:6379, conn-sec: 14.13, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: IncrDecrFloatingPointAsync, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=19,Free=32748,Min=4,Max=32767), POOL: (Threads=31,QueuedItems=124,CompletedItems=2706,Timers=38), v: 2.8.61.44828 (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-19_13_32_46.trx Error: StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: Assert.Equal() Failure: Values differ Expected: 6379 Actual: 7000

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: System.TimeoutException : Connect timeout

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=7KiB, inbound=0KiB, 5947ms elapsed, timeout is 5000ms), command=EXEC, next: MULTI, inst: 0, qu: 4, qs: 42, aw: True, bw: CheckingForTimeoutComplete, rs: ReadAsync, ws: Flushed, in: 555, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, sync-ops: 729, async-ops: 306, serverEndpoint: 127.0.0.1:6379, conn-sec: 13.13, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: IncrDecrFloatingPointAsync, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=18,Free=32749,Min=4,Max=32767), POOL: (Threads=31,QueuedItems=109,CompletedItems=2700,Timers=35), v: 2.8.61.44828 (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-19_13_32_46.trx Error: StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=7KiB, inbound=0KiB, 5947ms elapsed, timeout is 5000ms), command=EXPIRE, next: MULTI, inst: 0, qu: 4, qs: 42, aw: True, bw: CheckingForTimeoutComplete, rs: ReadAsync, ws: Flushed, in: 555, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, sync-ops: 729, async-ops: 306, serverEndpoint: 127.0.0.1:6379, conn-sec: 13.13, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: IncrDecrFloatingPointAsync, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=18,Free=32749,Min=4,Max=32767), POOL: (Threads=31,QueuedItems=110,CompletedItems=2700,Timers=35), v: 2.8.61.44828 (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-19_13_32_46.trx Error: StackExchange.Redis.RedisServerException : CROSSSLOT Keys in request don't hash to the same slot

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: StackExchange.Redis.RedisServerException : CROSSSLOT Keys in request don't hash to the same slot

Failed test found in: test-results/_pkrvmq0rgcvqdmg_2025-07-19_13_32_46.trx Error: StackExchange.Redis.RedisServerException : CROSSSLOT Keys in request don't hash to the same slot

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_52.trx Error: Assert.Equal() Failure: Strings differ ↓ (pos 0) Expected: "CPU" Actual: "miscellaneous" ↑ (pos 0)

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: Assert.Equal() Failure: Values differ Expected: 1 Actual: 0

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: Assert.Equal() Failure: Values differ Expected: 6379 Actual: 7000

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: Assert.Equal() Failure: Values differ Expected: 1 Actual: null

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.trx Error: StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot

Failed test found in: test-results/runneradmin_runnervm51nrn_2025-07-19_13_35_57.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