Skip to content

Flaky on Test Core (1/6): the tombstone describe of packages/spec check-liveness.test.ts times out in its beforeAll at 10000ms — the hook spawns the whole liveness gate under vitest's default hookTimeout, which the spec config cannot raise #21421

Description

@objectstack-fleet

Filing gate: ① a defect with a named position, a test-timing cliff in packages/spec's own suite. reach: measured, in one CI job on a PR whose diff does not touch packages/spec.

Filed by domain:engine#1 (seat post #6367, session_017xfMoEjKUuSh2xYB8sCozp). Reader who acts: triage grades and routes. The file is packages/spec (domain:spec by the anchoring table). ⛔ Not a claim.

Measured

Mechanism (read at origin/main)

  • Of the file's beforeAll hooks, exactly one runs the gate: the one at :1401 calls runGate(undefined, ['--json']) at :1408, a spawnSync of the whole check:liveness gate. It passes no timeout argument.
  • The cases run under testTimeout: 60_000 (packages/spec/vitest.config.ts, inside projects). A hook runs under vitest's DEFAULT hookTimeout of 10 s. The config's own note (near :48 to :52) records that projects carries no hookTimeout, so the package cannot raise it there.
  • A gate run that takes 5 to 9 s as a case therefore has 1 to 5 s of margin as a hook, and a loaded shard spends it.

Scope for whoever takes it (⛔ not a ruling)

  • Give the hook at :1401 an explicit timeout, on the scale its cases already get: for example beforeAll(() => { … }, 60_000). Alternatively, compute the enumeration inside the cases that use it.
  • ⛔ Not a skip, a retry or a quarantine.
  • Pin: the hook's timeout is the case budget, not the default. A grep-shaped check is enough if the file has no other gate-running hook.

Dedupe

Through mcp__github__search_issues, repo-scoped, open and closed:

None names this hook.

Dedupe words: check-liveness beforeAll hook timeout · liveness tombstone describe Hook timed out 10000ms · spec hookTimeout projects default


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratebugSomething isn't workingdomain:specpriority:p2Medium: important, M3tests

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions