Skip to content

Flaky test-inspector-port-cluster #19038

Description

@sethbrenith
  • Version: v10.0.0-pre
  • Platform: Windows Server 2012 R2 (6.3.9600), 64 bit
  • Subsystem: test

On a node-chakracore testing machine, we recently saw the following failures in test-inspector-port-cluster:

Starting inspector on 127.0.0.1:1025 failed: permission denied
Starting inspector on 127.0.0.1:1026 failed: permission denied

This is because the machine in question happens to have other processes listening on 1025 and 1026. Since any process could be using any port number, this test seems inherently flaky (except when run on CI machines, where the machine configuration is well-known). Is there a way to mark a test as expected to pass in CI but possibly flaky on dev machines? Alternately, is there a way to improve this test so that it is robust against failing to get the port numbers it wants?

Activity

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

    flaky-testIssues and PRs involving tests that fail intermittently in CI.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions