You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bounded-work's largest diffFlowchart case runs close to the default test timeout under coverage #42
packages/core/graph/projection/src/bounded-work.unit.test.ts asserts work counts, but each case still runs under Vitest's default per-test timeout, and the largest cases are close to it under coverage instrumentation in CI. "diffFlowchart reading an unchanged flowchart of diamonds sharing a run half of which leads somewhere" passes on recent main runs but timed out in https://github.com/ExaDev/process-graph/actions/runs/38111508236 on #41, where the Test job also builds and tests the bundled process-graph package alongside it, and the same file timed out under the pre-push hook on a loaded machine while passing when run alone.
The property is about work, so the failure is the clock: the case's input size or its timeout needs to come from the work it does rather than the default.
Activity
test(projection): run the work-growth cases without a clock bound
test(projection): run the work-growth cases without a clock bound