Skip to content

✅Unit Testing Status Check (main branch) #134

✅Unit Testing Status Check (main branch)

✅Unit Testing Status Check (main branch) #134

Triggered via pull request October 10, 2024 19:24
Status Success
Total duration 1m 24s
Artifacts

unit-test-status-check.yml

on: pull_request_target
PackageMonster Test Status Check  /  Print & Validate Run DotNet Tests Workflow
4s
PackageMonster Test Status Check / Print & Validate Run DotNet Tests Workflow
PackageMonster Test Status Check  /  ...  /  Resolve Project File Path
17s
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
PackageMonster Test Status Check  /  Run Unit Tests
36s
PackageMonster Test Status Check / Run Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

11 warnings and 3 notices
PackageMonster Test Status Check / Run Unit Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PackageMonster Test Status Check / Print & Validate Run DotNet Tests Workflow
The 'net-sdk-version' workflow input is valid.
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
DotNet Lib Release Script URL: https:/raw.githubusercontent.com/KinsonDigital/Infrastructure/v13.6.3/cicd/scripts
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
Set output 'project-file-path' set to a value of '/home/runner/work/PackageMonster/PackageMonster/Testing/PackageMonsterTests/PackageMonsterTests.csproj'.