Test a fix in minutes: capture a run's step and replay it locally on Free #340
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Verifying a fix means waiting on a production run that takes hours or days: #336 waited for a resume, #338 for one Visual check, #306 for one spec-test fan-out. The sims are fast but use a scripted model, so they can't show how a real model behaves. Today we stopped, resumed and reran whole projects to watch one step.
Fix
refs/osf/ckpt/…/entry, as a git bundle), the run's frozen settings, its recorded graph and brief, and the attempt's transcript, including which models served it.tools/demo.sh free-up, the real pinned router) starts a run at that step from the capsule and runs it, either pinned to the models that served the incident or on today's chain. It honours the run's privacy choices, and the fake forge takes any push.Done when
A production step is captured and replayed on the laptop in minutes, on Free and scripted, and an issue can close on a test or sim plus a local Free replay, without waiting on a production run.
Shipped in #343 (deployed, production on
c3407b8) and #348 (tooling only, merged with[skip ci]). Changereplay-a-stepis archived, with the new specstep-replay.Verified on run 159's Visual check (attempt 1), the incident behind #338:
./tools/replay.sh capture '<step address>' --attempt 1: 0.9 s from production.scripted: 24 s. The captured turns ran on today's code, and the judge's 7browsersubagent calls were refused.free: 47 min on real Free models, in Braid's image. Production's attempt ran 66 min with no report; the replay wrote one.Fixed while verifying (#348):
How to use it:
docs/testing.md, "Replaying a step" and "Closing an issue".