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
perf(bench): scope timeout to diffctx call only, not git ops
Outer kill switch on the worker covered ensure_repo + apply_as_commit
+ build_diff_context. On warm-cache Python repos git ops are ~1s so
the 20s budget covered diffctx. On non-Python repos with thousands
of files (vscode, mui, polybench) `git worktree add` alone is 30-60s,
exhausting the timeout before diffctx even starts. Result: 100%
timeout on polybench / multi_swebench / contextbench despite the
algorithm being capable of finishing under 20s.
Move the threading.Timer + os._exit(137) wrapper into the eval_fn
itself, scoped narrowly around build_diff_context (single-cell path)
and compute_scored_state + per-cell select_with_params (cached path).
Workers read DIFFCTX_BENCH_TIMEOUT_SEC from env; orchestrators set
it before pool spawn.
Git operations (clone, worktree add, gold-patch apply, reset_to_parent)
now run uninstrumented because they are benchmark scaffolding, not
the algorithm under measurement.
0 commit comments