Skip to content

WindowsInstaller.Tests.ps1 test WMF link invoke tests failing... #13478

Closed

Description

Steps to reproduce

Invoke-Pester WindowsInstaller.Tests.ps1

Expected 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'.

Activity

  1. added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Aug 18, 2020
  2. daxian-dbw commented on Aug 19, 2020

    @daxian-dbw
    Member

    Travis Plunk (@TravisEz13), if the that WMF 4 link is not coming back, then we potentially need to change the link in the installer script.

  3. TravisEz13 commented on Aug 19, 2020

    @TravisEz13
    Member

    Sounds right, I think anyone can change the link.

  4. iSazonov commented on Aug 20, 2020

    @iSazonov
    Collaborator
  5. daxian-dbw commented on Aug 20, 2020

    @daxian-dbw
    Member

    Joey Aiello (@joeyaiello) and Sean Wheeler (@sdwheeler), can you please check with someone from the download center to see if it's intentional to remove the WMF 4 download link?

  6. joeyaiello commented on Aug 20, 2020

    @joeyaiello
    Contributor

    Yeah, we're following up.

  7. joeyaiello commented on Dec 14, 2020

    @joeyaiello
    Contributor

    Still looking into seeing what can be done here, would love to know if this is impacting anyone today out in the real world.

  8. iSazonov commented on Dec 15, 2020

    @iSazonov
    Collaborator

    Is it all about Windows 7 support? If intention is to support Windows 7 in .Net 6.0 I think we still need WMF 4.0 with updates.

  9. iSazonov commented on Jan 18, 2021

    @iSazonov
    Collaborator

    I guess .Net 6.0 will support Windows 7. And question is will we support the next LTS version PowerShell 7.2 on Windows 7? If yes, maybe MSFT approve distributing WMF 4 in PowerShell 7.2 packages as an optional unsupported update?

  10. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  11. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  12. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  13. microsoft-github-policy-service commented on Nov 23, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally 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 moreWG-Maintainers-Buildspecific to affecting the build

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions