Skip to content

Benchmark and Duplex Pipe Concurrent Usage Fixes #362

Benchmark and Duplex Pipe Concurrent Usage Fixes

Benchmark and Duplex Pipe Concurrent Usage Fixes #362

Triggered via pull request September 15, 2023 22:31
Status Failure
Total duration 3m 30s
Artifacts

dotnet.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
build
Process completed with exit code 1.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L88
The variable 'e' is declared but never used
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L17
Non-nullable field '_client' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L18
Non-nullable field '_server' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L20
Non-nullable field '_log' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNet.IntegrationTests/Pipes/NexusServerTests_NexusDuplexPipe.cs#L89
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.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L88
The variable 'e' is declared but never used
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L17
Non-nullable field '_client' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L18
Non-nullable field '_server' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNetBenchmarks/InvocationBenchmarks.cs#L20
Non-nullable field '_log' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: src/NexNet.IntegrationTests/Pipes/NexusServerTests_NexusDuplexPipe.cs#L89
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.