WIP v3 #2274
CI.yml
on: pull_request
StackExchange.Redis (Ubuntu)
3m 8s
StackExchange.Redis (Windows Server 2022)
6m 7s
Annotations
11 errors and 4 warnings
|
StackExchange.Redis (Ubuntu)
Failed test were found and 'fail-on-error' option is set to true
|
|
StackExchange.Redis (Ubuntu)
Process completed with exit code 1.
|
|
ConfigTests.ExpectedFields (RESP3):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
↑ (pos 44)
|
|
ConfigTests.ExpectedFields (RESP2):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
↑ (pos 44)
|
|
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.
|
|
GetServerTestsStandalone.GetServerWithDefaultKey(explicitNull: True) (RESP2):
/_/tests/StackExchange.Redis.Tests/GetServerTests.cs#L84
System.InvalidOperationException : It was not possible to resolve a connection to the server owning the specified key
|
|
ConfigTests.ExpectedFields (RESP3):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
Γåæ (pos 43)
|
|
ConfigTests.ExpectedFields (RESP2):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [┬╖┬╖┬╖, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
Γåæ (pos 43)
|
|
ConfigTests.ExpectedFields (RESP3):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
↑ (pos 44)
|
|
ConfigTests.ExpectedFields (RESP2):
/_/tests/StackExchange.Redis.Tests/ConfigTests.cs#L25
Assert.Equal() Failure: Collections differ
Expected: [···, "syncTimeout", "tieBreaker", "Tunnel", "user"]
Actual: [···, "syncTimeout", "tieBreaker", "Tunnel", "user", "WriteMode"]
↑ (pos 44)
|
|
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)
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>0xzq1aQAAAACa+Kig7eD7T4PsW5xzgGL5RE0yRURHRTA4MDkARWRnZQ==
|
|
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400
|