Skip to content

Flaky tests under full-suite load + Docker-dependent tests need skip guard #582

Closed

Description

@diberry

Problem

When running the full test suite (~177 test files, ~4989 tests), approximately 24 tests fail intermittently due to two unrelated categories:

1. Docker-dependent tests (~15 failures)

Tests in \ est/cli/init.test.ts\ and \ est/init-prompt.test.ts\ require Docker Desktop to be running. When Docker is not available, they fail with:
\
failed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine
\\

Suggested fix: Add a skip guard that checks for Docker availability before running these tests (e.g., \describe.skipIf(!dockerAvailable)).

2. Timing/flaky tests under resource contention (~9 failures)

Tests in \ est/speed-gates.test.ts, \ est/streams.test.ts, \ est/template-sync.test.ts, \ est/repl-ux-fixes.test.ts, and \ est/human-journeys.test.ts\ fail when the full suite runs with 22 parallel workers but pass individually when run in isolation.

Symptoms:

  • Vitest worker timeout errors (\Timeout calling onTaskUpdate)
  • \ENOTEMPTY: directory not empty, rmdir\ during test cleanup
  • Timing assertions fail under load (speed gates)

Suggested fix: Increase timeout margins for speed-gate tests, add retry for cleanup operations, or reduce parallelism for resource-sensitive test files.

Impact

These are pre-existing on dev/main — not introduced by any specific PR. They affect CI reliability and cause false negatives in PR checks.

Environment

  • Windows 11, Node.js 20+
  • Vitest with 22 parallel workers
  • Docker Desktop not always running

squad obo dina

Activity

  1. bradygaster commented on Mar 24, 2026

    @bradygaster
    Collaborator

    formatting issues again

  2. added
    bugSomething isn't working
    squadSquad triage inbox — Lead will assign to a member
    on Mar 24, 2026
  3. github-actions commented on Mar 24, 2026

    @github-actions
    Contributor

    📋 Assigned to FIDO (Quality Owner)

    Issue: #582 — Flaky tests under full-suite load + Docker-dependent tests need skip guard

    FIDO will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    FIDO, work on issue #582

  4. github-actions commented on Mar 24, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #582 — Flaky tests under full-suite load + Docker-dependent tests need skip guard
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  5. diberry commented on Mar 31, 2026

    @diberry
    ContributorAuthor

    🔄 Ralph status: Closing as duplicate of #677, which was filed specifically to fix this issue. PR #679 addresses both. Tracking continues on #677.

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

    bugSomething isn't workinggo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions