Skip to content

chore: Adds macOS CI pipeline to GitHub Actions workflow #1785

chore: Adds macOS CI pipeline to GitHub Actions workflow

chore: Adds macOS CI pipeline to GitHub Actions workflow #1785

Triggered via pull request July 23, 2025 18:36
Status Failure
Total duration 19m 21s
Artifacts

CI.yml

on: pull_request
StackExchange.Redis (Ubuntu)
2m 53s
StackExchange.Redis (Ubuntu)
StackExchange.Redis (Windows Server 2022)
11m 18s
StackExchange.Redis (Windows Server 2022)
StackExchange.Redis (macOS)
19m 14s
StackExchange.Redis (macOS)
Fit to window
Zoom out
Zoom in

Annotations

15 errors, 2 warnings, and 2 notices
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.
AbortOnConnectFailTests.DisconnectAndReconnectThrowsConnectionExceptionSync (RESP2): /_/tests/StackExchange.Redis.Tests/AbortOnConnectFailTests.cs#L36
StackExchange.Redis.RedisConnectionException : The message timed out in the backlog attempting to send because no connection became available (1000ms) - Last Connection Exception: UnableToConnect (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 1000s, state: ConnectedEstablishing, mgr: 9 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.9.2.34048, command=PING, timeout: 1000, inst: 0, qu: 0, qs: 12, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Flushed, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 1, serverEndpoint: 127.0.0.1:6379, conn-sec: 1.51, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: runnervmatg8e(SE.Redis-v2.9.2.34048), IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=5,Free=32762,Min=4,Max=32767), v: 2.9.2.34048 (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 (None, 0-read, last-recv: 0) on 127.0.0.1:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 0s ago, last-write: 0s ago, unanswered-write: 0s ago, keep-alive: 1000s, state: ConnectedEstablishing, mgr: 9 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.9.2.34048
StackExchange.Redis (macOS)
HttpError: Resource not accessible by integration
RespProtocolTests.CheckCommandResult (RESP2): /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L229
StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.
RespProtocolTests.CheckCommandResult (RESP2): /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L229
StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.
RespProtocolTests.CheckCommandResult (RESP2): /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L229
StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.
RespProtocolTests.CheckCommandResult (RESP2): /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L229
StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.
RespProtocolTests.CheckCommandResult (RESP2): /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L229
StackExchange.Redis.RedisServerException : ERR DEBUG command not allowed. If the enable-debug-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.
RespProtocolTests.ConnectWithBrokenHello(command: "BONJOUR": /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L103
StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
RespProtocolTests.ConnectWithBrokenHello(command: "HELLO": /_/tests/StackExchange.Redis.Tests/RespProtocolTests.cs#L103
StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
SentinelTests.SentinelRole (RESP2): /_/tests/StackExchange.Redis.Tests/SentinelTests.cs#L142
StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
SentinelTests.SentinelGetSentinelAddressesTest (RESP2): /_/tests/StackExchange.Redis.Tests/SentinelTests.cs#L436
StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
SentinelTests.SentinelReplicasAsyncTest (RESP2): /_/tests/StackExchange.Redis.Tests/SentinelTests.cs#L417
StackExchange.Redis.RedisConnectionException : It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
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>09iuBaAAAAADxmKPmpz+9SZafc1xQbBdYUEFPRURHRTA1MDcARWRnZQ==
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400
StackExchange.Redis (macOS)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
StackExchange.Redis (macOS)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520