Skip to content
Run Pester Tests

1.0.9 features #4

Sign in to view logs

1.0.9 features

1.0.9 features #4

Triggered via pull request September 7, 2025 20:15
@kormic911kormic911
synchronize #10
1.0.9-Features
Status Failure
Total duration 1m 26s
Artifacts –

run-unit-tests.yml

on: pull_request
Pester test (On Linux)
56s
Pester test (On Linux)
Pester test (On Windows)
1m 22s
Pester test (On Windows)
Pester test (On macOS)
59s
Pester test (On macOS)
Fit to window
Zoom out
Zoom in

Annotations

26 errors, 55 warnings, and 1 notice
Pester test (On Linux)
[-] /home/runner/work/devsetup/devsetup/DevSetup/Private/Providers/Powershell/Uninstall-PowershellModules.Tests.ps1 failed with:
Pester test (On Linux)
[-] /home/runner/work/devsetup/devsetup/DevSetup/Private/Providers/Powershell/Install-PowershellModules.Tests.ps1 failed with:
Pester test (On Linux)
[-] /home/runner/work/devsetup/devsetup/DevSetup/Private/Providers/Core/Install-CoreDependencies.Tests.ps1 failed with:
Pester test (On Linux)
[-] /home/runner/work/devsetup/devsetup/DevSetup/Private/Commands/Uninstall-DevSetupEnv.Tests.ps1 failed with:
Pester test (On Linux)
[-] /home/runner/work/devsetup/devsetup/DevSetup/Private/Commands/Install-DevSetupEnv.Tests.ps1 failed with:
Pester test (On Linux)
[-] Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning 68ms (67ms|1ms)
Pester test (On Linux)
[-] Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message 54ms (53ms|1ms)
Pester test (On Linux)
[-] Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message 56ms (54ms|1ms)
Pester test (On Linux)
[-] Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose 51ms (50ms|1ms)
Pester test (On Linux)
[-] Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null 1.15s (1.15s|2ms)
Pester test (On macOS)
Process completed with exit code 1.
Pester test (On macOS)
[-] Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning 36ms (36ms|0ms)
Pester test (On macOS)
[-] Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message 43ms (43ms|0ms)
Pester test (On macOS)
[-] Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message 29ms (28ms|0ms)
Pester test (On macOS)
[-] Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose 48ms (48ms|0ms)
Pester test (On macOS)
[-] Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null 40ms (40ms|1ms)
Pester test (On Windows)
[-] Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning 55ms (55ms|1ms)
Pester test (On Windows)
[-] Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message 67ms (66ms|0ms)
Pester test (On Windows)
[-] Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message 55ms (55ms|0ms)
Pester test (On Windows)
[-] Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose 55ms (54ms|0ms)
Pester test (On Windows)
[-] Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null 127ms (126ms|0ms)
Pester test (On Windows)
[-] Install-ChocolateyPackage.When Write-ChocolateyCache fails after install.Should write warning and return false 17ms (16ms|1ms)
Pester test (On Windows)
[-] Install-ChocolateyPackage.When installation fails (non-zero exit code).Should write error and return false 22ms (21ms|1ms)
Pester test (On Windows)
[-] Install-ChocolateyPackage.When installing with version and params.Should build the correct choco command 30ms (28ms|1ms)
Pester test (On Windows)
[-] Install-ChocolateyPackage.When package is installed but version does not match.Should uninstall and reinstall the package 17ms (16ms|1ms)
Pester test (On Windows)
[-] Install-ChocolateyPackage.When package is already installed and version matches.Should return true immediately 41ms (40ms|1ms)
Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null failed: /#L0
testResults.xml [took 1s]
Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning failed: /#L0
testResults.xml [took 0s]
Install-DevSetupEnv.When environment file does not exist.Should write error and return failed: /#L0
testResults.xml [took 0s]
Install-DevSetupEnv.When YAML parsing fails.Should write error and return failed: /#L0
testResults.xml [took 0s]
Install-DevSetupEnv.When all dependencies install and no commands are present.Should install dependencies and write status failed: /#L0
testResults.xml [took 0s]
Install-DevSetupEnv.When commands are present and executed.Should execute all commands failed: /#L0
testResults.xml [took 0s]
Install-DevSetupEnv.When a command entry is missing the command property.Should skip and warn failed: /#L0
testResults.xml [took 0s]
Uninstall-DevSetupEnv.When environment file does not exist.Should write error and return failed: /#L0
testResults.xml [took 0s]
Uninstall-DevSetupEnv.When YAML parsing fails.Should write error and return failed: /#L0
testResults.xml [took 0s]
Uninstall-DevSetupEnv.When all uninstallers succeed.Should call all uninstallers and write status failed: /#L0
testResults.xml [took 0s]
Uninstall-DevSetupEnv.When a component uninstaller fails.Should continue calling other uninstallers failed: /#L0
testResults.xml [took 0s]
Uninstall-DevSetupEnv.When an exception occurs during uninstall.Should write error and return failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When NuGet installation fails.Should return false and write error failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When manifest is missing or has no required modules.Should return true and write warning failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When required module installation fails.Should return false and write error failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When required modules include empty names.Should skip empty module names and return true failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When all core dependencies install successfully on Windows.Should install everything and return true failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When Chocolatey installation fails on Windows.Should return false and write error failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When Git installation fails on Windows.Should return false and write error failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When Scoop installation fails on Windows.Should return false and write error failed: /#L0
testResults.xml [took 0s]
Install-CoreDependencies.When all core dependencies install successfully on non-Windows.Should skip Windows-only installs and return true failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When YAML configuration is missing PowerShell modules.Should return false failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When YAML configuration is missing dependencies.Should return false failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When AllUsers scope is specified but not running as admin.Should return false failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When modules are installed successfully (string format).Should install all modules and return true failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When modules are installed successfully (object format).Should install all modules and return true failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When some modules fail to install.Should continue and return true failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When module entry is empty or missing name.Should skip invalid entries and return true failed: /#L0
testResults.xml [took 0s]
Install-PowershellModules.When an exception occurs during installation.Should catch and return false failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When YAML configuration is missing PowerShell modules.Should return false and warn failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When YAML configuration is missing dependencies.Should return false and warn failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When AllUsers scope is specified but not running as admin.Should return false failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When modules are uninstalled successfully (string format).Should uninstall all modules and return true failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When modules are uninstalled successfully (object format).Should uninstall all modules and return true failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When some modules fail to uninstall.Should continue and return true failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When module entry is empty or missing name.Should skip invalid entries and return true failed: /#L0
testResults.xml [took 0s]
Uninstall-PowershellModules.When an exception occurs during uninstallation.Should catch and return false failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning failed: /#L0
testResults.xml [took 0s]
Install-ChocolateyPackage.When package is already installed and version matches.Should return true immediately failed: /#L0
testResults.xml [took 0s]
Install-ChocolateyPackage.When package is installed but version does not match.Should uninstall and reinstall the package failed: /#L0
testResults.xml [took 0s]
Install-ChocolateyPackage.When installing with version and params.Should build the correct choco command failed: /#L0
testResults.xml [took 0s]
Install-ChocolateyPackage.When installation fails (non-zero exit code).Should write error and return false failed: /#L0
testResults.xml [took 0s]
Install-ChocolateyPackage.When Write-ChocolateyCache fails after install.Should write warning and return false failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When EnvironmentsProjectUri is not a .git URL and GitHub API fails.Should write error and return null failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When repository path already exists.Should not clone and should write verbose failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository fails.Should write failed status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Install-GitRepository succeeds.Should write OK status message failed: /#L0
testResults.xml [took 0s]
Initialize-DevSetupEnvs.When Optimize-DevSetupEnvs is called.Should call Optimize-DevSetupEnvs after cloning failed: /#L0
testResults.xml [took 0s]
Pester test (On Windows)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677