Skip to content

Updated UnitTests to use the same strongnaming logic as the main SDK #128

Updated UnitTests to use the same strongnaming logic as the main SDK

Updated UnitTests to use the same strongnaming logic as the main SDK #128

Triggered via pull request August 27, 2024 18:39
Status Failure
Total duration 1m 58s
Artifacts

main.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
managed-build
The process 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' failed with exit code 1
managed-build
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/setup-msbuild@v1.0.2, microsoft/vstest-action@v1.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
managed-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v2, microsoft/setup-msbuild@v1.0.2, microsoft/vstest-action@v1.0.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
managed-build
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/
managed-build
No files were found with the provided path: TestResults. No artifacts will be uploaded.