Add Initial Metrics #1394
Annotations
5 errors and 1 warning
|
tests/StackExchange.Redis.Tests/AbortOnConnectFailTests.cs#L69
StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (100ms) - 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: 100s, state: Connecting, mgr: 9 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.131.40903, command=PING, timeout: 100, 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: fv-az612-336(SE.Redis-v2.6.131.40903), IOCP: (Busy=0,Free=1000,Min=2,Max=1000), WORKER: (Busy=3,Free=32764,Min=2,Max=32767), POOL: (Threads=4,QueuedItems=6,CompletedItems=248,Timers=17), v: 2.6.131.40903 (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: 100s, state: Connecting, mgr: 9 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.131.40903
|
tests/StackExchange.Redis.Tests/AbortOnConnectFailTests.cs#L45
StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (100ms) - Last Connection Exception: UnableToConnect on 127.0.0.1:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 1s ago, last-write: 1s ago, keep-alive: 100s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.131.40903, command=PING, timeout: 100, 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: 5 of 10 available, clientName: fv-az612-336(SE.Redis-v2.6.131.40903), IOCP: (Busy=0,Free=1000,Min=2,Max=1000), WORKER: (Busy=15,Free=32752,Min=2,Max=32767), POOL: (Threads=16,QueuedItems=0,CompletedItems=681,Timers=30), v: 2.6.131.40903 (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: 1s ago, last-write: 1s ago, keep-alive: 100s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.6.131.40903
|
tests/StackExchange.Redis.Tests/Issues/Issue2507.cs#L36
Assert.False() Failure
Expected: False
Actual: True
|
|
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/
|
The logs for this run have expired and are no longer available.
Loading