multi geo support #2217
CI.yml
on: pull_request
StackExchange.Redis (Ubuntu)
2m 56s
StackExchange.Redis (Windows Server 2022)
6m 16s
Annotations
5 errors and 2 warnings
|
StackExchange.Redis (Windows Server 2022)
Failed test were found and 'fail-on-error' option is set to true
|
|
StackExchange.Redis (Windows Server 2022)
Process completed with exit code 1.
|
|
MovedUnitTests.KeyMigrationFollowed(allowFollowRedirects: True) (RESP2):
/_/tests/StackExchange.Redis.Tests/MovedUnitTests.cs#L50
StackExchange.Redis.RedisTimeoutException : The message timed out in the backlog attempting to send because no connection became available, command=GET, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Idle, last-in: 191, cur-in: 0, sync-ops: 0, async-ops: 4, serverEndpoint: 127.0.0.1:6380, conn-sec: 15.03, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: runnervmixnmc(SE.Redis-v2.11.20.56507), PerfCounterHelperkeyHashSlot: 15004, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=1,Free=32766,Min=4,Max=32767), POOL: (Threads=6,QueuedItems=0,CompletedItems=129715,Timers=15), v: 2.11.20.56507 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
|
|
MovedUnitTests.KeyMigrationFollowed(allowFollowRedirects: False) (RESP2):
/_/tests/StackExchange.Redis.Tests/MovedUnitTests.cs#L50
StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: ProtocolFailure on 127.0.0.1:6379/Interactive, Flushed/ComputeResult, last: ECHO, origin: SetResultCore, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: ConnectedEstablishing, mgr: 8 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.11.20.56507, command=SET, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Idle, last-in: 16, cur-in: 0, sync-ops: 0, async-ops: 2, serverEndpoint: 127.0.0.1:6379, conn-sec: n/a, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: runnervmixnmc(SE.Redis-v2.11.20.56507), PerfCounterHelperkeyHashSlot: 15004, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=1,Free=32766,Min=4,Max=32767), POOL: (Threads=30,QueuedItems=0,CompletedItems=123341,Timers=15), v: 2.11.20.56507 (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 : ProtocolFailure on 127.0.0.1:6379/Interactive, Flushed/ComputeResult, last: ECHO, origin: SetResultCore, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: ConnectedEstablishing, mgr: 8 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.11.20.56507
|
|
MultiGroupTests.BasicMultiGroupTests.SelectByLatency (RESP2):
/_/tests/StackExchange.Redis.Tests/MultiGroupTests/BasicMultiGroupTests.cs#L58
Assert.Equal() Failure: Values differ
Expected: Unspecified/canada:6379
Actual: Unspecified/germany:6379
|
|
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>0j+uqaQAAAACFxzUIgRoTS65b9jQ0eRK4UEhYMzFFREdFMDUxMgBFZGdl
|
|
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400
|