Skip to content

chore: target tests to .net8.0 #745

chore: target tests to .net8.0

chore: target tests to .net8.0 #745

Triggered via pull request January 14, 2025 18:37
Status Success
Total duration 22m 47s
Artifacts 1

ci.yml

on: pull_request
Matrix: Validate 5.2
Validate 5.2 Samples (msbuild)
11m 9s
Validate 5.2 Samples (msbuild)
Validation Check
8s
Validation Check
Publish Dev
0s
Publish Dev
Publish Prod
0s
Publish Prod
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 20 warnings
Validate 5.2 Samples (msbuild)
Assets file 'D:\a\uno.resizetizer\uno.resizetizer\samples\5.2\Uno52ResizetizerTests\Uno52ResizetizerTests\obj\project.assets.json' doesn't have a target for 'net8.0-android'. Ensure that restore has run and that you have included 'net8.0-android' in the TargetFrameworks for your project.
Validate 5.2 Samples (msbuild)
Assets file 'D:\a\uno.resizetizer\uno.resizetizer\samples\5.2\Uno52ResizetizerTests\Uno52ResizetizerTests\obj\project.assets.json' doesn't have a target for 'net8.0-android'. Ensure that restore has run and that you have included 'net8.0-android' in the TargetFrameworks for your project.
Build: src/Resizetizer/test/UnitTests/MSBuildTaskFixture.cs#L13
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Validate 5.2 (ubuntu-latest, Release)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Validate 5.2 (ubuntu-latest, Release)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 (ubuntu-latest, Debug)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Validate 5.2 (ubuntu-latest, Debug)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 (windows-latest, Debug)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
The desktop TargetFramework must be placed first in the TargetFrameworks property in order for WSL debugging to work, when mobile targets are also used. (See https://aka.platform.uno/UNOB0014)
Validate 5.2 Samples (msbuild)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 (macos-15, Release)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 (windows-latest, Release)
No files were found with the provided path: .\logs. No artifacts will be uploaded.
Validate 5.2 (macos-15, Debug)
No files were found with the provided path: .\logs. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
NuGet Expired
41.5 MB