[Tests] Upgrade to xUnit v3 #1737
CI.yml
on: pull_request
StackExchange.Redis (Ubuntu)
3m 9s
StackExchange.Redis (Windows Server 2022)
6m 54s
Annotations
15 errors and 3 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.
|
|
PubSubMultiserverTests.ClusterNodeSubscriptionFailover (RESP3):
/_/tests/StackExchange.Redis.Tests/PubSubMultiserverTests.cs#L27
System.AggregateException : One or more errors occurred. (Assert.True() Failure
Expected: True
Actual: False) ($XunitDynamicSkip$There were 3 private and 0 ambient exceptions; expected 0.)
---- Assert.True() Failure
Expected: True
Actual: False
---- $XunitDynamicSkip$There were 3 private and 0 ambient exceptions; expected 0.
|
|
SyncContextTests.SyncConfigure (RESP2):
/_/tests/StackExchange.Redis.Tests/SyncContextTests.cs#L69
Assert.True() Failure
Expected: True
Actual: False
|
|
StackExchange.Redis (Windows Server 2022)
Failed test were found and 'fail-on-error' option is set to true
|
|
TransactionTests.BasicTranWithSortedSetScoreCountExistsCondition(member1HasScore: False:
/_/tests/StackExchange.Redis.Tests/TransactionTests.cs#L922
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
TransactionTests.BasicTranWithSortedSetScoreCountExistsCondition(member1HasScore: False:
/_/tests/StackExchange.Redis.Tests/TransactionTests.cs#L922
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
TransactionTests.BasicTranWithSortedSetScoreCountExistsCondition(member1HasScore: False:
/_/tests/StackExchange.Redis.Tests/TransactionTests.cs#L922
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
StreamTests.StreamConsumerGroupReadMultipleRestrictCount (RESP3):
/_/tests/StackExchange.Redis.Tests/StreamTests.cs#L939
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
StreamTests.StreamReadMultipleStreamsWithReadPastSecondStream (RESP3):
/_/tests/StackExchange.Redis.Tests/StreamTests.cs#L1689
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
StreamTests.StreamReadMultipleStreamsWithCount (RESP3):
/_/tests/StackExchange.Redis.Tests/StreamTests.cs#L1655
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
StreamTests.StreamConsumerGroupReadMultipleOneReadBeginningOneReadNew (RESP3):
/_/tests/StackExchange.Redis.Tests/StreamTests.cs#L824
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
HyperLogLogTests.MultiKeyLength (RESP3):
/_/tests/StackExchange.Redis.Tests/HyperLogLogTests.cs#L24
StackExchange.Redis.RedisCommandException : Multi-key operations must involve a single slot; keys can use 'hash tags' to help this, i.e. '{/users/12345}/account' and '{/users/12345}/contacts' will always be in the same slot
|
|
ScanTests.SortedSetScanLarge(pageSize: 10000) (RESP2):
/_/tests/StackExchange.Redis.Tests/ScanTests.cs#L445
StackExchange.Redis.RedisTimeoutException : Timeout performing ZSCAN (5000ms), inst: 0, qu: 0, qs: 0, aw: False, bw: SpinningDown, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 2548, async-ops: 9, serverEndpoint: 127.0.0.1:6379, conn-sec: 5.7, aoc: 1, mc: 1/1/0, mgr: 10 of 10 available, clientName: AddHashEveryWay, IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=16,Free=32751,Min=4,Max=32767), POOL: (Threads=17,QueuedItems=620,CompletedItems=170,Timers=17), v: 2.8.62.29502 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
|
|
ScriptingTests.SimpleRawScriptEvaluate (RESP3):
/_/tests/StackExchange.Redis.Tests/ScriptingTests.cs#L562
System.ArgumentException : The specified endpoint is not defined
Parameter name: endpoint
|
|
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>03qN7aAAAAADVVMxd8AC5SqfW93gxVYbqRE0yRURHRTA1MjEARWRnZQ==
|
|
StackExchange.Redis (Windows Server 2022)
Failed to restore: Cache service responded with 400
|