Bump NUnit from 3.13.3 to 4.1.0 #118
Annotations
10 errors and 11 warnings
|
UnitTests/CRC-CCITT.cs#L16
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CMAC.cs#L17
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CMAC.cs#L27
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/QRCodes.cs#L20
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CTR_DRBG.cs#L28
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CTR_DRBG.cs#L48
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CMAC.cs#L37
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CMAC.cs#L47
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CTR_DRBG.cs#L68
The name 'CollectionAssert' does not exist in the current context
|
|
UnitTests/CMAC.cs#L57
The name 'CollectionAssert' does not exist in the current context
|
|
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
ZWaveDotNet/CommandClassReports/EndPointCapabilities.cs#L7
Nullability of reference types in return type of 'string? object.ToString()' doesn't match implicitly implemented member 'string ICommandClassReport.ToString()' (possibly because of nullability attributes).
|
|
ZWaveDotNet/CommandClassReports/EndPointFindReport.cs#L7
Nullability of reference types in return type of 'string? object.ToString()' doesn't match implicitly implemented member 'string ICommandClassReport.ToString()' (possibly because of nullability attributes).
|
|
ZWaveDotNet/CommandClassReports/EndPointReport.cs#L6
Nullability of reference types in return type of 'string? object.ToString()' doesn't match implicitly implemented member 'string ICommandClassReport.ToString()' (possibly because of nullability attributes).
|
|
ZWaveDotNet/CommandClasses/ZWavePlus.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/Version.cs#L52
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/Unknown.cs#L15
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/TransportService.cs#L136
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/TimeParameters.cs#L55
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/SwitchAll.cs#L49
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
ZWaveDotNet/CommandClasses/SilenceAlarm.cs#L34
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
This job failed
Loading