Skip to content

flaky: parallel.test-child-process-fork-net #51813

Description

@mhdawson

Test

parallel.test-child-process-fork-net

Platform

Windows

Console output

Add description
Error Message
fail (1)
Stacktrace
---
duration_ms: 567.994
exitcode: 1
severity: fail
...

Build links

Additional information

No response

Activity

  1. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Feb 20, 2024
  2. joyeecheung commented on Feb 22, 2024

    @joyeecheung
    Member

    This has failed 14 PRs out of the last 100 CI runs.

    From a glance the test it's hard to tell what it is trying to do. It was added by dceebbf#diff-53a1141f9d431cc7d603359ba604d660819f5560b68895fb639dc988a34644c8 so I suppose the original intention was just to test that the socket can be sent over to the child. The messages based on connection order seems to be very brittle, I don't think we guarantee that if you fork multiple child processes, they are going to be ready to connect to the parent in the exact same order that you start them. Perhaps the test can be split so that each child process gets its own test. But that's just a guess, I am not 100% that's not breaking what the test was trying to check.

  3. joyeecheung commented on Feb 23, 2024

    @joyeecheung
    Member

    Actually I have a different theory. See #51841

  4. lpinca commented on Sep 7, 2024

    @lpinca
    Member

    Fixed in #51841.

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.windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions