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
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 touchpackages/spec.Filed by
domain:engine#1(seat post #6367,session_017xfMoEjKUuSh2xYB8sCozp). Reader who acts: triage grades and routes. The file ispackages/spec(domain:specby the anchoring table). ⛔ Not a claim.Measured
driver-sql/core/objectqlonly) at head7445ed5cd. CI run 37015237168, job 110864497182 (Test Core (1/6)).@objectstack/spec#testreported 1 failed and 599 passed test files. The one failure isscripts/liveness/check-liveness.test.ts > check:liveness — a tombstoned key may not be graded \live` ([finding] the liveness gate has no reading of aretiredKey()tombstone — a tombstoned key's row may claimliveand nothing objects (the mechanism behind #18304) #19062), at line 1401. The error isHook timed out in 10000ms`, and the describe's case was skipped behind it.mainis green onTest Core (1/6)for its last six commits (db3fee3dctoceb4a939b). So this is a load cliff, not a deterministic break.Mechanism (read at
origin/main)beforeAllhooks, exactly one runs the gate: the one at:1401callsrunGate(undefined, ['--json'])at:1408, aspawnSyncof the wholecheck:livenessgate. It passes no timeout argument.testTimeout: 60_000(packages/spec/vitest.config.ts, insideprojects). A hook runs under vitest's DEFAULThookTimeoutof 10 s. The config's own note (near:48to:52) records thatprojectscarries nohookTimeout, so the package cannot raise it there.Scope for whoever takes it (⛔ not a ruling)
:1401an explicit timeout, on the scale its cases already get: for examplebeforeAll(() => { … }, 60_000). Alternatively, compute the enumeration inside the cases that use it.Dedupe
Through
mcp__github__search_issues, repo-scoped, open and closed:hook.jsontimeoutas 'live' — the ledger marked itdeadwhen #15626 renamed it totimeoutMs#15839 is closed and on another subject.None names this hook.
Dedupe words:
check-liveness beforeAll hook timeout·liveness tombstone describe Hook timed out 10000ms·spec hookTimeout projects defaultGenerated by Claude Code