Skip to content

CI flake: TypeScript - Tests #6549

Closed as duplicate
Closed as duplicate

Description

@clockwork-labs-bot

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

  • TypeScript - Tests

Error:
❌ ERROR A callback threw Error: callback failed

Failed job runs:

Timeout detection:

  • none

Context:

  • none

Activity

  1. clockwork-labs-bot commented on Nov 10, 2026

    @clockwork-labs-bot
    ContributorAuthor

    Symptoms and root cause

    • Exact failed attempt: run 42835269793, job 129902259301, attempt 1, using Node 22.23.4.
    • All 506 runtime tests passed; typechecking reported no errors. The ticket's A callback threw Error: callback failed excerpt comes from the intentional negative test logs an error thrown by a callback and keeps the connection open, not the failure.
    • The subsequent recursive template build aborted in templates/chat-react-ts (tsc -b && vite build): Fatal error in , line 0, unreachable code, native stack V8_Fatal → LoadElimination::ReduceStoreField; exit status 133. The CI wrapper then exited 1. This establishes a Node/V8 optimizer abort, not a test assertion; the underlying trigger remains unproven.
    • Attempt 2, job 130069594356 succeeded, including the template build. No rerun was initiated for this followup.

    Duplicate selection

    • Reviewed all 100 OPEN issues in the 997-item Test flakes project across repositories, plus organization-wide OPEN searches for the fatal diagnostic, V8, and optimizer frame.
    • Select OPEN #5366 — CI flake: v8 internal error during build: same specific unreachable code / V8 fatal / exit-133 build-abort family, with explicit human consolidation and established incoming canonical duplicate relationships. This occurrence is in a template build and a different optimizer frame; those differences do not outweigh the matching fatal signature.
    • Silent build failures without a V8 diagnostic and bare segmentation faults are weaker matches. No closed issues were searched or inspected to reconstruct duplicate history.

    Proposed operations

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions