Skip to content

Test-Connection Force IPv4 with explicit PingOptions test failing on Linux platforms #6707

Closed

Description

A test failure related to Test-Connection is found in CI runs in the master branch and PR.
This test failure was seen in the CI build in the master branch after #6612 was merged.
Then it's seen again in the CI runs for PR #6660.

Build: https://ci.appveyor.com/project/PowerShell/powershell/build/v6.1.0-preview.9044

TEST FAILURES
Description: Force IPv4 with explicit PingOptions
Name:        Test-Connection.Ping.Force IPv4 with explicit PingOptions
message:
Expected exactly '8.8.8.8', but got 0.0.0.0.
stack-trace:
at <ScriptBlock>, C:\projects\powershell\test\powershell\Modules\Microsoft.PowerShell.Management\Test-Connection.Tests.ps1: line 98
98:             $result1.Replies[0].Address              | Should -BeExactly $realAddress

Activity

  1. daxian-dbw commented on Apr 23, 2018

    @daxian-dbw
    MemberAuthor
  2. iSazonov commented on Apr 25, 2018

    @iSazonov
    Collaborator

    The test uses external resources so it can sometimes fall. We seen the same while the web cmdlet tests used httpbin.org - WebListener solved this.
    We need to create a network emulator to solve this problem.

  3. changed the title [-]Failure in 'Test-Connection' test discovered in CI runs[/-] [+]Test-Connection Force IPv4 with explicit PingOptions test failing on Linux platforms[/+] on Feb 11, 2021
  4. 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.

  5. 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.

  6. 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.

  7. 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-BugIssue has been identified as a bug in the productRelease-TestingResolution-No ActivityIssue has had no activity for 6 months or moreWG-Cmdletsgeneral cmdlet issuesWG-Quality-Testissues in a test or in test infrastructure

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions