Bump xunit from 2.5.0 to 2.5.1 #50
build.yml
on: push
build-and-test-48
1m 57s
Matrix: build-and-test
Annotations
22 errors and 7 warnings
build-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L90
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L93
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L96
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L100
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L105
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L107
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L110
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L114
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L234
Test methods must 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-and-test (6.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L239
Test methods must 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-and-test (7.0)
The job was canceled because "_6_0" failed.
|
build-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L90
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L93
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L96
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L100
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L105
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L107
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L110
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L114
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L234
Test methods must 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-and-test (7.0):
BitPayFunctionalTest/BitPayFunctionalTest.cs#L239
Test methods must 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-and-test-48
Process completed with exit code 1.
|
build-and-test (6.0):
BitPay/Models/Payout/Payout.cs#L264
The result of the expression is always 'true' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-and-test (6.0):
BitPay/Models/Payout/Payout.cs#L264
The result of the expression is always 'true' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-and-test (7.0):
BitPay/Models/Payout/Payout.cs#L264
The result of the expression is always 'true' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-and-test (7.0):
BitPay/Models/Payout/Payout.cs#L264
The result of the expression is always 'true' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-and-test-48
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-and-test-48
Unexpected input(s) 'dotNetVersion', valid inputs are ['vswhere-path', 'vs-version']
|
build-and-test-48
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|