VMHyperV: Added the ability to enable or disable the TPM on a VM #215
Build #4.0.0-PR0215.5 had test failures
Details
- Failed: 12 (0.72%)
- Passed: 1,632 (97.49%)
- Other: 30 (1.79%)
- Total: 1,674
Annotations
Check failure on line 383 in Build log
azure-pipelines / dsccommunity.HyperVDsc
Build log #L383
PowerShell exited with code '1'.
Check failure on line 1827 in Build log
azure-pipelines / dsccommunity.HyperVDsc
Build log #L1827
PowerShell exited with code '1'.
Check failure on line 1334 in Build log
azure-pipelines / dsccommunity.HyperVDsc
Build log #L1334
PowerShell exited with code '1'.
azure-pipelines / dsccommunity.HyperVDsc
Error occurred in test script 'D:\a\1\s\tests\Integration\DSC_VMHost.Integration.Tests.ps1'
At D:\a\1\s\tests\Integration\DSC_VMHost_set.config.ps1:18 char:5
+ Import-DscResource -ModuleName 'xHyperV'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Could not find the module 'xHyperV'.
Raw output
at <ScriptBlock>, D:\a\1\s\tests\Integration\DSC_VMHost.Integration.Tests.ps1: line 41
azure-pipelines / dsccommunity.HyperVDsc
DSC_VMProcessor_Set_Integration.Configure VM.Should compile without throwing
Expected no exception to be thrown, but an exception "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The term 'xVMProcessor' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." was thrown from D:\a\1\s\tests\Integration\DSC_VMProcessor_set.config.ps1:1 char:1
+ configuration DSC_VMProcessor_Set_Config {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.Raw output
at <ScriptBlock>, D:\a\1\s\tests\Integration\DSC_VMProcessor.Integration.Tests.ps1: line 72
72: } | Should not throw
azure-pipelines / dsccommunity.HyperVDsc
DSC_VMProcessor_Set_Integration.Configure VM.should be able to call Get-DscConfiguration without throwing
Expected no exception to be thrown, but an exception "Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first." was thrown from D:\a\1\s\tests\Integration\DSC_VMProcessor.Integration.Tests.ps1:76 char:19
+ ... { Get-DscConfiguration -Verbose -ErrorAction Stop } | Sho ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.Raw output
at <ScriptBlock>, D:\a\1\s\tests\Integration\DSC_VMProcessor.Integration.Tests.ps1: line 76
76: { Get-DscConfiguration -Verbose -ErrorAction Stop } | Should Not throw
azure-pipelines / dsccommunity.HyperVDsc
DSC_VMProcessor_Set_Integration.Configure VM.Should have set the resource and all the parameters should match
Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first.
Raw output
at <ScriptBlock>, D:\a\1\s\tests\Integration\DSC_VMProcessor.Integration.Tests.ps1: line 81
81: $current = Get-DscConfiguration | Where-Object {