Skip to content

Fix #2679: connect/config: only access task.Result if we know it completed #1548

Fix #2679: connect/config: only access task.Result if we know it completed

Fix #2679: connect/config: only access task.Result if we know it completed #1548

Triggered via pull request March 19, 2024 14:02
Status Failure
Total duration 6m 0s
Artifacts

CI.yml

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

Annotations

3 errors and 1 warning
StackExchange.Redis (Windows Server 2022)
Failed test were found and 'fail-on-error' option is set to true
AbortOnConnectFailTests.DisconnectAndNoReconnectThrowsConnectionExceptionAsync(RESP2): _/tests/StackExchange.Redis.Tests/AbortOnConnectFailTests.cs#L78
Assert.Throws() Failure: Exception type was not an exact match Expected: typeof(StackExchange.Redis.RedisConnectionException) Actual: typeof(System.ObjectDisposedException) ---- System.ObjectDisposedException : Cannot access a disposed object. Object name: 'Connection is being finalized'.
StackExchange.Redis (Windows Server 2022)
Process completed with exit code 1.
StackExchange.Redis (Ubuntu)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.