Failed test found in: test-results/_fv-az986-119_2023-08-16_12_30_58.trx Error: Assert.Equal() Failure Expected: 6 Actual: 12

Failed test found in: test-results/_fv-az986-119_2023-08-16_12_30_58.trx Error: Assert.Equal() Failure Expected: 2 Actual: 3

Failed test found in: test-results/_fv-az986-119_2023-08-16_12_30_58.trx Error: Assert.True() Failure Expected: True Actual: False

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

Assert.True() Failure Expected: True Actual: False

Assert.Equal() Failure Expected: 6 Actual: 12

Assert.Equal() Failure Expected: 2 Actual: 3

Process completed with exit code 1.

Failed test found in: test-results/runneradmin_fv-az417-928_2023-08-16_12_33_57.trx Error: StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (100ms) - Last Connection Exception: UnableToConnect (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 100s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.134.1273, command=PING, timeout: 100, inst: 36, qu: 1, qs: 12, aw: False, bw: Inactive, rs: ReadAsync, ws: Flushed, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: 0.18, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: fv-az417-928(SE.Redis-v2.6.134.1273), IOCP: (Busy=0,Free=1000,Min=2,Max=1000), WORKER: (Busy=4,Free=32763,Min=2,Max=32767), POOL: (Threads=24,QueuedItems=5,CompletedItems=16290,Timers=75), v: 2.6.134.1273 (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 (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 100s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.134.1273

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

StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (100ms) - Last Connection Exception: UnableToConnect (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 100s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.134.1273, command=PING, timeout: 100, inst: 36, qu: 1, qs: 12, aw: False, bw: Inactive, rs: ReadAsync, ws: Flushed, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: 0.18, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: fv-az417-928(SE.Redis-v2.6.134.1273), IOCP: (Busy=0,Free=1000,Min=2,Max=1000), WORKER: (Busy=4,Free=32763,Min=2,Max=32767), POOL: (Threads=24,QueuedItems=5,CompletedItems=16290,Timers=75), v: 2.6.134.1273 (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 (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 100s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.134.1273

Process completed with exit code 1.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Test report summary exceeded limit of 65535 bytes and will be trimmed