Skip to content

test-file-write-stream4 is consistently flaky #56883

Closed as not planned
Closed as not planned
test-file-write-stream4 is consistently flaky#56883
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@jasnell
jasnell
opened on Feb 2, 2025

Test

test-file-write-stream4

Platform

No response

Console output

---
duration_ms: 120062.706
exitcode: -15
severity: fail
stack: timeout
...

Build links

Additional information

No response

Activity

  1. jasnell
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Feb 2, 2025

  2. jasnell commented on Feb 2, 2025

    @jasnell
    jasnell
    on Feb 2, 2025
    MemberAuthor

    Is this the process deadlock isssue or something else?

  3. lpinca commented on Feb 6, 2025

    @lpinca
    lpinca
    on Feb 6, 2025
    Member

    Yes, the underlying issue is #54918.

  4. joyeecheung commented on Apr 18, 2025

    @joyeecheung
    joyeecheung
    on Apr 18, 2025
    Member

    This can be traced as far back as 2021 nodejs/reliability#102
    In the last reliability report this is still failing 8 PRs out of the last 100 CI runs: nodejs/reliability#1177
    Considering we (sort of) know the cause but are unable to fix it for the time being, and this has been flaky for more than 3 years without promising remedy in the near future, I think we should just mark it as flaky for now and let it tracked by #54918

  5. github-actions commented on Apr 21, 2026

    @github-actions
    github-actionsbot
    on Apr 21, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  6. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 21, 2026

  7. github-actions commented on May 22, 2026

    @github-actions
    github-actionsbot
    on May 22, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  8. github-actions
    closed this as not plannedon May 22, 2026
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.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions