Skip to content

pages build and deployment #396

pages build and deployment

pages build and deployment #396

Triggered via dynamic March 27, 2026 14:12
Status Success
Total duration 40s
Artifacts 1

pages-build-deployment

on: dynamic
report-build-status
2s
report-build-status
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
StackExchange.Redis.Tests.Resp3HandshakeTests ► Resp3HandshakeTests.Handshake(client: Resp3, server: Resp2, flags: Authenticated | UsePubSub | UseDatabase) (RESP2): test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx#L0
Failed test found in: test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx Error: Assert.Single() Failure: The collection contained 2 items Collection: ["msg payload", "msg payload"]
StackExchange.Redis.Tests.SentinelTests ► SentinelTests.SentinelPrimariesAsyncTest (RESP2): test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx#L0
Failed test found in: test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx Error: Assert.StartsWith() Failure: String start does not match String: "s_down,o_down,master,failover_in_progress" Expected start: "master"
StackExchange.Redis.Tests.SentinelTests ► SentinelTests.SentinelPrimariesTest (RESP2): test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx#L0
Failed test found in: test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx Error: Assert.StartsWith() Failure: String start does not match String: "s_down,o_down,master,failover_in_progress" Expected start: "master"
StackExchange.Redis.Tests.SentinelTests ► SentinelTests.SentinelPrimaryAsyncTest (RESP2): test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx#L0
Failed test found in: test-results/runneradmin_runnervm6wf0k_2026-03-27_14_17_40.trx Error: Assert.StartsWith() Failure: String start does not match String: "s_down,o_down,master,failover_in_progress" Expected start: "master"
StackExchange.Redis.Tests.AbortOnConnectFailTests ► AbortOnConnectFailTests.DisconnectAndNoReconnectThrowsConnectionExceptionAsync (RESP2): test-results/runneradmin_runnervm6wf0k_2026-03-27_14_18_31.trx#L0
Failed test found in: test-results/runneradmin_runnervm6wf0k_2026-03-27_14_18_31.trx Error: StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (1000ms) - Last Connection Exception: UnableToConnect (0-read, 0-sent) 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: 1000s, state: Connecting, last-heartbeat: never, global: 4s ago, v: 3.0.6.37346, command=PING, timeout: 1000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, in: 0, in-pipe: 0, last-in: 0, cur-in: 0, lm: 8/85/77/0, sync-ops: 0, async-ops: 1, serverEndpoint: 127.0.0.1:6379, conn-sec: 0, aoc: 0, mc: 1/1/0, clientName: runnervm6wf0k(SE.Redis-v3.0.6.37346), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=4,Free=32763,Min=4,Max=32767), POOL: (Threads=11,QueuedItems=0,CompletedItems=6526,Timers=40), v: 3.0.6.37346 (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 (0-read, 0-sent) 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: 1000s, state: Connecting, last-heartbeat: never, global: 4s ago, v: 3.0.6.37346
build
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/upload-artifact@v4. 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/
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
github-pages Expired
178 KB
sha256:ebbb8ae7af9f8be3900c97e2d170398f400775f7eccd591cbe10aa00858ca84d