Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests\Integration\xServiceSet.Integration.Tests.ps1: Doesn't Work Outside of AppVeyor #585

Closed
mhendric opened this issue Mar 6, 2019 · 0 comments · Fixed by #594
Closed
Labels
bug The issue is a bug.

Comments

@mhendric
Copy link
Contributor

mhendric commented Mar 6, 2019

Details of the scenario you tried and the problem that is occurring

Tests in 'xServiceSet.Integration.Tests.ps1' currently fail when run from outside of AppVeyor. These tests should be adjusted to run on any supported system.

Verbose logs showing the problem

Executing script C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\xServiceSet.Integration.Tests.ps1
WARNING: There is no operation running currently. Stop will return without any action.

  Describing xServiceSet Integration Tests

    Context Edit all possible properties of one service except BuiltInAccount
WARNING: There is no operation running currently. Stop will return without any action.
      [-] Error occurred in Context block 0ms
        COMException: The group name could not be found.
        ExtendedTypeSystemException: The following exception occurred while retrieving member "SetPassword": "The group name could not be found.
        "
        at Get-AppVeyorAdministratorCredential, C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\CommonTestHelper.psm1: line 685
        at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\xServiceSet.Integration.Tests.ps1: line 141
        at DescribeImpl, C:\Program Files\WindowsPowerShell\Modules\Pester\4.7.1\Functions\Describe.ps1: line 199

    Context Edit BuiltInAccount of two services
WARNING: There is no operation running currently. Stop will return without any action.
      [+] Should compile and apply the MOF without throwing 2.24s
      [+] Should not have removed service 1 11ms
      [+] Should have set the state  of service 1 to Running (default action of xService) 4ms
      [+] Should have set the start name of service 1 to the specified built-in account name 2ms
      [+] Should not have removed service 2 8ms
      [+] Should have set the state  of service 2 to Running (default action of xService) 1ms
      [+] Should have set the start name of service 2 to the specified built-in account name 1ms

    Context Remove two services
WARNING: There is no operation running currently. Stop will return without any action.
      [+] Should compile and apply the MOF without throwing 1.29s
      [+] Should have removed service 1 9ms
      [+] Should have removed service 2 11ms
WARNING: There is no operation running currently. Stop will return without any action.

The operating system the target node is running

PS C:> Get-ComputerInfo -Property @(
'OsName',
'OsOperatingSystemSKU',
'OSArchitecture',
'WindowsVersion',
'WindowsBuildLabEx',
'OsLanguage',
'OsMuiLanguages')

OsName : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture : 64-bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : en-US
OsMuiLanguages : {en-US}

Version and build of PowerShell the target node is running

PS C:> $PSVersionTable

Name Value


PSVersion 5.1.17763.316
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.316
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Version of the DSC module that was used ('dev' if using current dev branch)

dev

@mhendric mhendric added bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community. in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels Mar 6, 2019
@kwirkykat kwirkykat removed the in progress The issue is being actively worked on by someone. label Mar 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug.
Projects
None yet
2 participants