Skip to content

Support multi-DB cluster usage on valkey #2284

Support multi-DB cluster usage on valkey

Support multi-DB cluster usage on valkey #2284

Triggered via pull request March 20, 2026 14:05
Status Failure
Total duration 6m 18s
Artifacts

CI.yml

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

Annotations

9 errors and 5 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.
KeyIdleAsyncTests.IdleTimeAsync (RESP2): /_/tests/StackExchange.Redis.Tests/KeyIdleAsyncTests.cs#L10
System.ObjectDisposedException : Cannot access a disposed object. Object name: 'Connection is being disposed'.
HyperLogLogTests.SingleKeyLength (RESP2): /_/tests/StackExchange.Redis.Tests/HyperLogLogTests.cs#L9
System.ObjectDisposedException : Cannot access a disposed object. Object name: 'Connection is being disposed'.
Issues.Issue1103Tests.LargeUInt64StoredCorrectly(value: 142205255210238005: /_/tests/StackExchange.Redis.Tests/Issues/Issue1103Tests.cs#L10
StackExchange.Redis.RedisTimeoutException : Timeout performing GET (5000ms), next: GET 10.0.2-Issue1103Tests-Issue1103Tests-LargeUInt64StoredCorrectlyR2, inst: 15, qu: 0, qs: 1, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 2, cur-in: 0, lm: 7/476/467/2, sync-ops: 2, async-ops: 0, serverEndpoint: 127.0.0.1:6379, conn-sec: 5.06, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: LargeUInt64StoredCorrectly, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=8,Free=32759,Min=4,Max=32767), POOL: (Threads=22,QueuedItems=7,CompletedItems=112737,Timers=29), v: 2.12.8.7044 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
StreamTests.StreamAutoClaim_MissingKey (RESP3): /_/tests/StackExchange.Redis.Tests/StreamTests.cs#L204
StackExchange.Redis.RedisTimeoutException : Timeout performing UNLINK (5000ms), next: UNLINK 10.0.2-StreamTests-StreamTests-StreamAutoClaim_MissingKeyR31774015891497, inst: 25, qu: 0, qs: 1, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, lm: 7/476/467/2, sync-ops: 39166, async-ops: 7509, serverEndpoint: 127.0.0.1:6379, conn-sec: 5.36, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: BasicOps, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=8,Free=32759,Min=4,Max=32767), POOL: (Threads=22,QueuedItems=7,CompletedItems=112737,Timers=29), v: 2.12.8.7044 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
RespProtocolTests.CheckLuaResult(script: "return redis.pcall('hgetall': /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L125
StackExchange.Redis.RedisTimeoutException : Timeout performing UNLINK (5000ms), next: UNLINK 10.0.2-RespProtocolTests-RespProtocolTests-CheckLuaResultR2, inst: 23, qu: 0, qs: 2, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 4, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, lm: 7/476/467/2, sync-ops: 39395, async-ops: 10757, serverEndpoint: 127.0.0.1:6379, conn-sec: 25.63, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: GetAllocatorStats, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=8,Free=32759,Min=4,Max=32767), POOL: (Threads=22,QueuedItems=7,CompletedItems=112737,Timers=29), v: 2.12.8.7044 (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 (Ubuntu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, dorny/test-reporter@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
StackExchange.Redis (Windows Server 2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/test-reporter@v1, Vampire/setup-wsl@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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>0fVS9aQAAAAAhq+ZO9Up9RZqRtUCS92jIQ0hHRURHRTE5MTAARWRnZQ==
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400