Skip to content

Refactor IO "read" core logic #2225

Refactor IO "read" core logic

Refactor IO "read" core logic #2225

Triggered via pull request March 9, 2026 15:36
Status Failure
Total duration 6m 16s
Artifacts

CI.yml

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

Annotations

17 errors and 3 warnings
StackExchange.Redis (Ubuntu)
Failed test were found and 'fail-on-error' option is set to true
StackExchange.Redis (Ubuntu)
Process completed with exit code 1.
InProcPubSubTests.TestBasicPubSubFireAndForget (RESP3): /_/tests/StackExchange.Redis.Tests/PubSubTests.cs#L167
StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5996ms elapsed, timeout is 5000ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in-pipe: 0, last-in: 7, cur-in: 7, sync-ops: 2, async-ops: 4, serverEndpoint: 127.0.0.1:6379, conn-sec: 6, aoc: 1, mc: 1/1/0, clientName: runnervm0kj6c(SE.Redis-v3.0.22.35442), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=2,Free=32765,Min=4,Max=32767), POOL: (Threads=30,QueuedItems=0,CompletedItems=156515,Timers=29), v: 3.0.22.35442 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
InProcPubSubTests.TestBasicPubSubFireAndForget (RESP2): /_/tests/StackExchange.Redis.Tests/PubSubTests.cs#L167
StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5991ms elapsed, timeout is 5000ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in-pipe: 0, last-in: 19, cur-in: 19, sync-ops: 2, async-ops: 4, serverEndpoint: 127.0.0.1:6379, conn-sec: 6, aoc: 1, mc: 1/1/0, clientName: runnervm0kj6c(SE.Redis-v3.0.22.35442), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=4,Free=32763,Min=4,Max=32767), POOL: (Threads=30,QueuedItems=0,CompletedItems=123777,Timers=32), v: 3.0.22.35442 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
ConfigTests.ExpectedFields (RESP3): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] ↑ (pos 44)
ConfigTests.ExpectedFields (RESP2): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] ↑ (pos 44)
StackExchange.Redis (Windows Server 2022)
Failed test were found and 'fail-on-error' option is set to true
ClusterShardedTests.KeepSubscribedThroughSlotMigrationAsync (RESP2): /_/tests/StackExchange.Redis.Tests/ClusterShardedTests.cs#L257
StackExchange.Redis.RedisServerException : ERR Please use SETSLOT only with masters.
ClusterShardedTests.SubscribeToWrongServerAsync(sharded: True) (RESP3): /_/tests/StackExchange.Redis.Tests/ClusterShardedTests.cs#L211
Assert.Equal() Failure: Values differ Expected: 127.0.0.1:7003 Actual: 127.0.0.1:7000
ClusterShardedTests.SubscribeToWrongServerAsync(sharded: True) (RESP2): /_/tests/StackExchange.Redis.Tests/ClusterShardedTests.cs#L211
Assert.Equal() Failure: Values differ Expected: 127.0.0.1:7003 Actual: 127.0.0.1:7000
InProcPubSubTests.TestBasicPubSubFireAndForget (RESP2): /_/tests/StackExchange.Redis.Tests/PubSubTests.cs#L167
StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5031ms elapsed, timeout is 5000ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in-pipe: 0, last-in: 19, cur-in: 19, sync-ops: 2, async-ops: 4, serverEndpoint: 127.0.0.1:6379, conn-sec: 5.05, aoc: 1, mc: 1/1/0, clientName: runnervmixnmc(SE.Redis-v3.0.22.35442), IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=4,Free=32763,Min=4,Max=32767), v: 3.0.22.35442 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
ConfigTests.ExpectedFields (RESP3): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] Γåæ (pos 43)
ConfigTests.ExpectedFields (RESP2): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] Γåæ (pos 43)
InProcPubSubTests.TestBasicPubSubFireAndForget (RESP3): /_/tests/StackExchange.Redis.Tests/PubSubTests.cs#L167
StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5015ms elapsed, timeout is 5000ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in-pipe: 0, last-in: 7, cur-in: 7, sync-ops: 2, async-ops: 4, serverEndpoint: 127.0.0.1:6379, conn-sec: 5.02, aoc: 1, mc: 1/1/0, clientName: runnervmixnmc(SE.Redis-v3.0.22.35442), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=3,Free=32764,Min=4,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=155462,Timers=31), v: 3.0.22.35442 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
InProcPubSubTests.TestBasicPubSubFireAndForget (RESP2): /_/tests/StackExchange.Redis.Tests/PubSubTests.cs#L167
StackExchange.Redis.RedisTimeoutException : Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5000ms elapsed, timeout is 5000ms), command=PING, next: PING, inst: 0, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in-pipe: 0, last-in: 19, cur-in: 19, sync-ops: 2, async-ops: 4, serverEndpoint: 127.0.0.1:6379, conn-sec: 5, aoc: 1, mc: 1/1/0, clientName: runnervmixnmc(SE.Redis-v3.0.22.35442), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=2,Free=32765,Min=4,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=148464,Timers=33), v: 3.0.22.35442 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
ConfigTests.ExpectedFields (RESP3): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] ↑ (pos 44)
ConfigTests.ExpectedFields (RESP2): /_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"] Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"] ↑ (pos 44)
StackExchange.Redis (Windows Server 2022)
Test report summary exceeded limit of 65535 bytes and will be trimmed
StackExchange.Redis (Windows Server 2022)
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>0MOmuaQAAAADsnxoGixXWRLUVGzI/9eyHRE0yRURHRTA3MTIARWRnZQ==
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400