Skip to content

Bump version to 1.0 #79

Bump version to 1.0

Bump version to 1.0 #79

Triggered via push April 6, 2024 12:05
Status Failure
Total duration 31s
Artifacts

dotnet.yml

on: push
build-test-and-push
23s
build-test-and-push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
build-test-and-push
Process completed with exit code 1.
build-test-and-push
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithReturn.cs#L27
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithWaitAndReturn.cs#L42
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithWaitAndReturn.cs#L42
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L58
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L47
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithReturn.cs#L27
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithWaitAndReturn.cs#L42
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build-test-and-push: Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithWaitAndReturn.cs#L42
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)