Skip to content

Fix CMake build in test subdirectories #150

Fix CMake build in test subdirectories

Fix CMake build in test subdirectories #150

Triggered via pull request July 4, 2023 20:00
Status Success
Total duration 47m 13s
Artifacts

amd64_macos_make_dotnet.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
make
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
make
- Add lib or ref assemblies for the net6.0 target framework
make: ortools/linear_solver/csharp/LinearExpr.cs#L19
'LinearExpr' defines operator == or operator != but does not override Object.Equals(object o)
make: ortools/linear_solver/csharp/LinearExpr.cs#L19
'LinearExpr' defines operator == or operator != but does not override Object.GetHashCode()
make: build_make/dotnet/Google.OrTools/ortools/constraint_solver/BaseObject.cs#L68
'BaseObject.ToString()' hides inherited member 'object.ToString()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
make: build_make/dotnet/Google.OrTools/ortools/constraint_solver/Constraint.cs#L18
'Constraint' defines operator == or operator != but does not override Object.Equals(object o)
make: build_make/dotnet/Google.OrTools/ortools/constraint_solver/Constraint.cs#L18
'Constraint' defines operator == or operator != but does not override Object.GetHashCode()
make: build_make/dotnet/Google.OrTools/ortools/linear_solver/Variable.cs#L13
'Variable' defines operator == or operator != but does not override Object.Equals(object o)
make: build_make/dotnet/Google.OrTools/ortools/linear_solver/Variable.cs#L13
'Variable' defines operator == or operator != but does not override Object.GetHashCode()
make: ortools/linear_solver/csharp/LinearConstraint.cs#L21
'LinearConstraint.ToString()' hides inherited member 'object.ToString()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
make
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
make: temp_dotnet/sat/NursesSat/NursesSat.cs#L161
Unreachable code detected
make: temp_dotnet/sat/NursesSat/NursesSat.cs#L161
Unreachable code detected
make: temp_dotnet/sat/ScheduleRequestsSat/ScheduleRequestsSat.cs#L203
The variable 'isWorking' is assigned but its value is never used
make: temp_dotnet/sat/ScheduleRequestsSat/ScheduleRequestsSat.cs#L203
The variable 'isWorking' is assigned but its value is never used
make: temp_dotnet/graph/FlowTests/FlowTests.cs#L71
The literal or constant value MaxFlow.Status.OPTIMAL should be passed as the 'expected' argument in the call to 'Assert.Equal(expected, actual)' in method 'testMaxFlow' on type 'FlowTest'.
make: temp_dotnet/graph/FlowTests/FlowTests.cs#L48
The literal or constant value MinCostFlow.Status.OPTIMAL should be passed as the 'expected' argument in the call to 'Assert.Equal(expected, actual)' in method 'testMinCostFlow' on type 'FlowTest'.
make: temp_dotnet/graph/FlowTests/FlowTests.cs#L71
The literal or constant value MaxFlow.Status.OPTIMAL should be passed as the 'expected' argument in the call to 'Assert.Equal(expected, actual)' in method 'testMaxFlow' on type 'FlowTest'.
make: temp_dotnet/graph/FlowTests/FlowTests.cs#L48
The literal or constant value MinCostFlow.Status.OPTIMAL should be passed as the 'expected' argument in the call to 'Assert.Equal(expected, actual)' in method 'testMinCostFlow' on type 'FlowTest'.