Skip to content

remoed deleted projects #230

remoed deleted projects

remoed deleted projects #230

Triggered via push March 11, 2024 05:40
Status Failure
Total duration 1m 19s
Artifacts

build.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 17 warnings
build (ubuntu-latest): test/SuperSocket.Benchmarks/CurrentSend.cs#L7
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L5
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L10
The type or namespace name 'PipeChannel<>' could not be found (are you missing a using directive or an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L15
The type or namespace name 'ChannelOptions' could not be found (are you missing a using directive or an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L22
The type or namespace name 'CloseReason' could not be found (are you missing a using directive or an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/CurrentSend.cs#L36
The type or namespace name 'ChannelOptions' could not be found (are you missing a using directive or an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/CurrentSend.cs#L7
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L5
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L10
The type or namespace name 'PipeChannel<>' could not be found (are you missing a using directive or an assembly reference?)
build (ubuntu-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L15
The type or namespace name 'ChannelOptions' could not be found (are you missing a using directive or an assembly reference?)
build (windows-latest)
The job was canceled because "ubuntu-latest" failed.
build (windows-latest)
The operation was canceled.
build (macos-latest)
The job was canceled because "ubuntu-latest" failed.
build (macos-latest): test/SuperSocket.Benchmarks/CurrentSend.cs#L7
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (macos-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L5
The type or namespace name 'Channel' does not exist in the namespace 'SuperSocket' (are you missing an assembly reference?)
build (macos-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L10
The type or namespace name 'PipeChannel<>' could not be found (are you missing a using directive or an assembly reference?)
build (macos-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L15
The type or namespace name 'ChannelOptions' could not be found (are you missing a using directive or an assembly reference?)
build (macos-latest): test/SuperSocket.Benchmarks/TransparentPipeChannel.cs#L22
The type or namespace name 'CloseReason' could not be found (are you missing a using directive or an assembly reference?)
build (macos-latest): test/SuperSocket.Benchmarks/CurrentSend.cs#L36
The type or namespace name 'ChannelOptions' could not be found (are you missing a using directive or an assembly reference?)
build (macos-latest)
The operation was canceled.
build (ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: 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 (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L35
Public method 'TestNormalRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L68
Public method 'TestMiddleBreak' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L103
Public method 'TestFragmentRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L143
Public method 'TestBatchRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L191
Public method 'TestBreakRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ClientTest.cs#L163
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L35
Public method 'TestNormalRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L68
Public method 'TestMiddleBreak' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L103
Public method 'TestFragmentRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (ubuntu-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L143
Public method 'TestBatchRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L35
Public method 'TestNormalRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L68
Public method 'TestMiddleBreak' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L103
Public method 'TestFragmentRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L143
Public method 'TestBatchRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ProtocolTestBase.cs#L191
Public method 'TestBreakRequest' on test class 'ProtocolTestBase' should be marked as a Theory. (https://xunit.github.io/xunit.analyzers/rules/xUnit1013)
build (macos-latest): test/SuperSocket.Tests/ClientTest.cs#L163
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)