Skip to content

interpreting server_mode field (to support Valkey 8+ cluster) #2344

interpreting server_mode field (to support Valkey 8+ cluster)

interpreting server_mode field (to support Valkey 8+ cluster) #2344

Triggered via pull request April 8, 2026 10:48
Status Failure
Total duration 5m 49s
Artifacts

CI.yml

on: pull_request
StackExchange.Redis (Ubuntu)
2m 57s
StackExchange.Redis (Ubuntu)
StackExchange.Redis (Windows Server 2022)
5m 45s
StackExchange.Redis (Windows Server 2022)
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
StackExchange.Redis (Ubuntu)
HttpError: Resource not accessible by integration
StackExchange.Redis (Windows Server 2022)
HttpError: Resource not accessible by integration
StackExchange.Redis (Windows Server 2022)
Process completed with exit code 1.
StreamTests.StreamConsumerGroupAutoClaim_SingleStream (RESP2): /_/tests/StackExchange.Redis.Tests/StreamTests.cs#L668
Assert.Empty() Failure: Collection was not empty Collection: [StackExchange.Redis.StreamEntry, StackExchange.Redis.StreamEntry]
TransactionTests.BasicTranWithHashLengthCondition(value: "": /_/tests/StackExchange.Redis.Tests/TransactionTests.cs#L417
System.Threading.Tasks.TaskCanceledException : A task was canceled.
ListTests.ListMultiPopSingleKeyAsync (RESP3): /_/tests/StackExchange.Redis.Tests/ListTests.cs#L832
StackExchange.Redis.RedisTimeoutException : Timeout performing LPUSH (5000ms), next: MULTI, inst: 24, qu: 0, qs: 6, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 1, cur-in: 0, lm: 17/810/783/10, sync-ops: 37439, async-ops: 7424, serverEndpoint: 127.0.0.1:6379, conn-sec: 24.68, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: HashFieldPersistNoExpireTime, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=9,Free=32758,Min=4,Max=32767), POOL: (Threads=25,QueuedItems=6,CompletedItems=88705,Timers=28), v: 2.12.18.65247 (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. Node.js 20 will be removed from the runner on September 16th, 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. Node.js 20 will be removed from the runner on September 16th, 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)
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>0lzLWaQAAAABdmJB+VTavRaoNX6OuiI/3UEhMMzBFREdFMDIxNgBFZGdl
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400