Build & Tests

build(deps): Bump xunit from 2.5.0 to 2.5.1 #122

Triggered via pull request September 18, 2023 16:42

dependabot[bot]

synchronize #60

dependabot/nuget/xunit-2.5.1

Status Failure

Total duration 15m 52s

Artifacts 2

This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

cicd.yml

on: pull_request

Build & Tests / ... / Validate Code Formatting

3m 1s

Build & Tests / ... / Run CodeQL

15m 39s

Build & Tests / ... / Prepare Test Matrix

Matrix: Build & Tests / Tests .NET / Testing

Build & Tests / ... / Building

3m 12s

Build & Tests / ... / Publish NuGet Packages

Annotations

1 error and 55 warnings

Build & Tests / Validate Code formatting / Validate Code Formatting

Process completed with exit code 2.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L44

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L25

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L28

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L63

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L25

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L28

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L44

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L63

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L25

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting: src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L28

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.

Build & Tests / Validate Code formatting / Validate Code Formatting

The 'dotnet-quality' input can be used only with .NET SDK version in A.B, A.B.x, A, A.x and A.B.Cxx formats where the major tag is higher than 5. You specified: 5.x. 'dotnet-quality' input is ignored.

Build & Tests / Tests .NET / Testing (UnitTest)

Build & Tests / Tests .NET / Testing (UnitTest): src/HealthChecks.SqlServer/tests/NetEvolve.HealthChecks.SqlServer.Tests.Unit/SqlServerCheckTests.cs#L25