Skip to content

broken the fork_signal_to_child test #3472

@vtjnash

Description

@vtjnash

I am somewhat suspicious that #3466 may have broken the fork_signal_to_child test, as UV_RUN_ONCE is a very risky thing to test, and we always initialize the loop with pending work.

Originally posted by @vtjnash in #3466 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions