Skip to content

Enable GitHub CI

Enable GitHub CI #1951

Triggered via pull request October 18, 2023 23:09
Status Failure
Total duration 12m 28s
Artifacts

ci.yml

on: pull_request
Matrix: test-backend
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 15 warnings
test-backend (windows-latest)
Process completed with exit code 1.
test-backend (windows-latest)
Process completed with exit code 1.
test-backend (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1.1.0, gradle/wrapper-validation-action@v1.0.3, microsoft/setup-msbuild@v1.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-backend (windows-latest)
ProjectReference 'D:\a\resharper-fsharp\resharper-fsharp\ReSharper.FSharp\src\FSharp\FSharp.TypeProviders.Protocol\FSharp.TypeProviders.Protocol.csproj' was resolved using '.NETFramework,Version=v4.7.2' instead of the project target framework '.NETCoreApp,Version=v3.1'. This project may not be fully compatible with your project.
test-backend (windows-latest)
ProjectReference 'D:\a\resharper-fsharp\resharper-fsharp\ReSharper.FSharp\src\FSharp\FSharp.ProjectModelBase\FSharp.ProjectModelBase.csproj' was resolved using '.NETFramework,Version=v4.7.2' instead of the project target framework '.NETCoreApp,Version=v3.1'. This project may not be fully compatible with your project.
test-backend (windows-latest)
ProjectReference 'D:\a\resharper-fsharp\resharper-fsharp\ReSharper.FSharp\src\FSharp\FSharp.Fantomas.Protocol\FSharp.Fantomas.Protocol.csproj' was resolved using '.NETFramework,Version=v4.7.2' instead of the project target framework '.NETCoreApp,Version=v6.0'. This project may not be fully compatible with your project.
test-backend (windows-latest): ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host/src/Hosts/TypeProvidersHost.cs#L25
'IRdEndpoint<int[], Unit>.Set(Func<Lifetime, int[], RdTask<Unit>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
test-backend (windows-latest): ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host/src/Hosts/TypeProvidersHost.cs#L25
'IRdEndpoint<int[], Unit>.Set(Func<Lifetime, int[], RdTask<Unit>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
test-backend (windows-latest): ReSharper.FSharp/src/FSharp/FSharp.Common/src/Util/FSharpCompilerAttributesUtil.fs#L10
This construct is deprecated. Use strongly typed properties (e.g. 'IntValue', 'BoolValue', 'StringValue' etc.) whenever is possible
test-backend (windows-latest): ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/FcsCheckerService.fs#L109
This construct is deprecated. Use separate test components (can be inherited from real ones)
test-backend (windows-latest): ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/FSharpScriptPsiModuleFactory.fs#L142
This construct is deprecated. Use the method with reason parameter
test-backend (windows-latest): ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/FcsProjectBuilder.fs#L157
This construct is deprecated. Use separate test components (can be inherited from real ones)
test-backend (windows-latest): ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Tree/ParameterOwnerMemberDeclarationNavigator.cs#L8
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
test-backend (windows-latest)
The `save-state` 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/
test-backend (windows-latest)
The `save-state` 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/
test-backend (windows-latest)
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/
test-backend (windows-latest)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.