Repository navigation
Remoting tests that target PowerShell 5.1 should be disabled consistently #4289
Description
WinRM (Windows only) based remoting tests require either a default or custom PowerShell endpoint, and currently endpoints are based on built-in PowerShell 5.1. Consequently many remoting tests do not work correctly and must be disabled. We should disable them in a consistent way, I think by using the -Pending switch.
Activity
SteveL-MSFT commentedon Jul 18, 2017
Instead of marking them
Pending, we may be able to fix them after #2671 gets mergedPaulHigin commentedon Jul 18, 2017
I somehow missed that PR, but yes part of that work should be to update all remoting tests so that they run on the new endpoints. I'll take a look at the PR this week.
PaulHigin commentedon Jul 18, 2017
Actually, that work is incomplete. We need to make all remoting cmdlets work, not just Enable-PSRemoting. I'll comment on the PR.
TravisEz13 commentedon Dec 6, 2017
Paul Higinbotham (@PaulHigin) Can this be closed?
microsoft-github-policy-service commentedon Nov 16, 2023
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.
microsoft-github-policy-service commentedon Nov 16, 2023
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.
microsoft-github-policy-service commentedon Nov 16, 2023
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.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.