-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Area-Maintainers-Buildspecific to affecting the buildspecific to affecting the buildIssue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more
Description
Steps to reproduce
Invoke-Pester WindowsInstaller.Tests.ps1Expected behavior
Tests pass
Actual behavior
WMF 4.0 link invocation fails.
Environment data
Name Value
---- -----
PSVersion 7.0.3
PSEdition Core
GitCommitId 7.0.3
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
This test checks for expected links in Product.wxs file, but then invokes the links to see if they are alive. Many times they are not and there is a retry loop. In this case WMF 4.0 link is not working. Don't know if the link was pulled on purpose.
However, this does not seem like a good test for PowerShell, as PowerShell has nothing to do whether these links work and if they don't should not cause PowerShell build to fail. I will mark the link invocation test as 'pending'.
Metadata
Metadata
Assignees
Labels
Area-Maintainers-Buildspecific to affecting the buildspecific to affecting the buildIssue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more