Migrate Pester test suite from v4 to v5 #12
ci.yml
on: pull_request
Matrix: test
Publish Test Results
17s
Annotations
30 errors and 8 warnings
|
Test (ubuntu-latest)
Process completed with exit code 1.
|
|
Test (ubuntu-latest)
[-] Returns $true if the module is installed 119ms (118ms|1ms)
|
|
Test (ubuntu-latest)
[-] Returns $false when it finds an existing module with a lower version than latest 91ms (90ms|1ms)
|
|
Test (ubuntu-latest)
[-] Returns $false when it finds an existing module with a lower version 97ms (96ms|1ms)
|
|
Test (ubuntu-latest)
[-] Returns $false when it doesn't find an existing module 113ms (113ms|1ms)
|
|
Test (ubuntu-latest)
[-] Returns $true when it finds an existing latest module 93ms (92ms|1ms)
|
|
Test (ubuntu-latest)
[-] Returns $true when it finds an existing module 107ms (106ms|1ms)
|
|
Test (ubuntu-latest)
[-] Runs Get-Package and Find-Package, skips Install-Package 96ms (95ms|1ms)
|
|
Test (ubuntu-latest)
[-] Skips Install-Package 121ms (118ms|2ms)
|
|
Test (ubuntu-latest)
[-] Context PSModuleGallery Type.Package Type PS7.Installs Packages failed
|
|
Test (macOS-latest)
Process completed with exit code 1.
|
|
Test (macOS-latest)
[-] Returns $true if the module is installed 86ms (86ms|0ms)
|
|
Test (macOS-latest)
[-] Returns $false when it finds an existing module with a lower version than latest 129ms (129ms|0ms)
|
|
Test (macOS-latest)
[-] Returns $false when it finds an existing module with a lower version 290ms (289ms|1ms)
|
|
Test (macOS-latest)
[-] Returns $false when it doesn't find an existing module 103ms (102ms|0ms)
|
|
Test (macOS-latest)
[-] Returns $true when it finds an existing latest module 89ms (89ms|1ms)
|
|
Test (macOS-latest)
[-] Returns $true when it finds an existing module 121ms (120ms|1ms)
|
|
Test (macOS-latest)
[-] Runs Get-Package and Find-Package, skips Install-Package 143ms (142ms|1ms)
|
|
Test (macOS-latest)
[-] Skips Install-Package 96ms (95ms|1ms)
|
|
Test (macOS-latest)
[-] Context PSModuleGallery Type.Package Type PS7.Installs Packages failed
|
|
Test (windows-latest)
[-] installs Chocolatey 3.56s (3.56s|2ms)
|
|
Test (windows-latest)
[-] Returns $true if the module is installed 112ms (111ms|1ms)
|
|
Test (windows-latest)
[-] Returns $false when it finds an existing module with a lower version than latest 76ms (76ms|1ms)
|
|
Test (windows-latest)
[-] Returns $false when it finds an existing module with a lower version 80ms (80ms|0ms)
|
|
Test (windows-latest)
[-] Returns $false when it doesn't find an existing module 67ms (67ms|0ms)
|
|
Test (windows-latest)
[-] Returns $true when it finds an existing latest module 79ms (79ms|0ms)
|
|
Test (windows-latest)
[-] Returns $true when it finds an existing module 71ms (70ms|1ms)
|
|
Test (windows-latest)
[-] Runs Get-Package and Find-Package, skips Install-Package 66ms (65ms|1ms)
|
|
Test (windows-latest)
[-] Skips Install-Package 72ms (70ms|2ms)
|
|
Test (windows-latest)
[-] Context PSModuleGallery Type.Package Type PS7.Installs Packages failed
|
|
Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test (ubuntu-latest)
No files were found with the provided path: ./Output/testResults.xml. No artifacts will be uploaded.
|
|
Test (macOS-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test (macOS-latest)
No files were found with the provided path: ./Output/testResults.xml. No artifacts will be uploaded.
|
|
Test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test (windows-latest)
No files were found with the provided path: ./Output/testResults.xml. No artifacts will be uploaded.
|
|
Publish Test Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish Test Results
Could not find any files for artifacts/**/*.xml
|