Skip to content

Fix #2778: Run CheckInfoReplication even with HeartbeatConsistencyChecks #1622

Fix #2778: Run CheckInfoReplication even with HeartbeatConsistencyChecks

Fix #2778: Run CheckInfoReplication even with HeartbeatConsistencyChecks #1622

Re-run triggered September 3, 2024 15:02
Status Failure
Total duration 3m 43s
Artifacts

CI.yml

on: pull_request
StackExchange.Redis (Ubuntu)
3m 34s
StackExchange.Redis (Ubuntu)
StackExchange.Redis (Windows Server 2022)
6m 14s
StackExchange.Redis (Windows Server 2022)
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
StackExchange.Redis.Tests.AbortOnConnectFailTests ► AbortOnConnectFailTests.DisconnectAndNoReconnectThrowsConnectionExceptionAsync(RESP2): test-results/_fv-az1114-89_2024-09-03_15_04_08.trx#L0
Failed test found in: test-results/_fv-az1114-89_2024-09-03_15_04_08.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: 2s ago, last-write: 2s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.14.51032, 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: fv-az1114-89(SE.Redis-v2.8.14.51032), IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=10,Free=32757,Min=4,Max=32767), POOL: (Threads=10,QueuedItems=45,CompletedItems=578,Timers=41), v: 2.8.14.51032 (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: 2s ago, last-write: 2s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.14.51032
StackExchange.Redis (Ubuntu)
Failed test were found and 'fail-on-error' option is set to true
AbortOnConnectFailTests.DisconnectAndNoReconnectThrowsConnectionExceptionAsync(RESP2): _/tests/StackExchange.Redis.Tests/AbortOnConnectFailTests.cs#L70
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: 2s ago, last-write: 2s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.14.51032, 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: fv-az1114-89(SE.Redis-v2.8.14.51032), IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=10,Free=32757,Min=4,Max=32767), POOL: (Threads=10,QueuedItems=45,CompletedItems=578,Timers=41), v: 2.8.14.51032 (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: 2s ago, last-write: 2s ago, keep-alive: 400s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.8.14.51032
StackExchange.Redis (Ubuntu)
Process completed with exit code 1.
StackExchange.Redis (Ubuntu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/