161 Commits

Author SHA1 Message Date
bench
13b19513fb quota: a full-context 400 on the half-open probe reopens the group
10-27 formal-qwen: after a CONNECT_FAILED cooldown the half-open probe was a
full context (400 CONTEXT_TOO_LONG). _finish only failed the generation, so
the group stayed HALF_OPEN, which admission never treats as ready: all five
lanes sent nothing for 4.5 h and paused on QUOTA_WAIT_BUDGET_EXHAUSTED.
The provider answered, so treat it like a successful probe (RECOVERING, 1).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 61d8f54d44a7f9e5e696edb1603fd405622e6abb)
2026-11-04 15:23:41 +08:00
bench
67303f7a06 execution: a paused rollout past its deadline after a reboot ends as DEADLINE_EXCEEDED
After a host reboot _reason() returned BOOT_CHANGED_RECONCILE_REQUIRED for every paused
execution before looking at the deadline, so one already past 24 h was offered for resume,
refused by resume() without saving why, and offered again. 10-25 after the Mac mini hang
seven rollouts looped ~43k times and held 7 lanes until they were cancelled by hand.

When the boot changed, judge a paused execution's deadline by wall time (the old boot's
monotonic clock means nothing). _resume_snapshot already settles EXECUTION_DEADLINE_EXCEEDED.

Checked on staging (r20261026-st): rollout made to look "previous boot, started 49 h ago,
paused 1 h"; the collector settled it as DEADLINE_EXCEEDED within a minute of start, no loop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 10d5546f884053c6d1bf062e140183ff172f70dc)
2026-11-04 15:23:41 +08:00
bench
24127dd3c1 scheduler: release a quarantined board of a paused rollout when the board is idle, from acquire
reconcile_leases only released boards of TERMINAL executions and only ran on manual reconcile, so a rollout
paused after a failed 07-board (10-24 16:02) kept the only S100P board quarantined for 6.5 hours. Acquire now
retries the proven-release path every 10 minutes while a slot is quarantined; a paused owner's board is freed
on the same proof as a terminal one (holder dead, no owned processes, live probe shows an idle board).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 71873e0ba1b1b987c80e78bcc0d93845202e81af)
2026-11-04 15:23:41 +08:00
bench
28d251207d quota: a rate limit sent as HTTP 400 is a rate limit (production 10-30)
Same classification as be22235 on salty-test. The FAT gateway answers an
account rate limit with 400 "RateLimitError"; it paused rollouts for good
as UPSTREAM_REJECTED. 05 moves to that gateway.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 11:18:05 +08:00
bench
dca5d0e09d salty offload: an archived rollout drops its whole workspace (production 10-29 11:00)
Same change as 4f27d61 on salty-test, salty_offload.py only. Archived
rollouts kept 34 GB of small workspace files on the VM, all in their tgz.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:00:43 +08:00
bench
36b7649a7f salty offload: export runs in the background so archiving keeps freeing disk (production hotfix 10-28 21:18)
Same change as 68028a2 on salty-test, salty_offload.py only. Production ran
the 4-6 h export in the loop and wrote 4-6G meanwhile; the VM disk hit 2G.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 23:18:11 +08:00
bench
31817a71fc speed_ref packs the platform code again; agent bench dev still does not
speed_ref exports the default graph with harness/tools inside bench dev; since 8fb9349 the dev bundle carried only
container_site, so a job without a cached export could not get a speed reference. salty_dev.execute takes an explicit
platform_code flag that only speed_ref passes; the agent's terminal path never sets it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 12:34:49 +08:00
bench
ea83762099 board_refs: install onnxruntime on a board that lacks it, from the kept wheels
Boards have no internet. configs/board-ort keeps a wheel per board python (cp310 S100P, cp312 S600, SHA256SUMS);
the first CPU measurement on a board without onnxruntime installs it into /userdata/bench-ort, and a board whose
python has no kept wheel fails that job's CPU reference with the pip download command to fetch one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:55:46 +08:00
bench
fd508fc513 board_refs: restore BOARD_* after building the ssh command; the registry check reads them for slot 0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:43:52 +08:00
bench
1dcf331c90 Gates: compute must run on the BPU; board latency budget and the original model on the board CPU as speed floors
- 06-hbm records the convolutions/matmuls hb_compile left on the CPU (its node table's ON column); G1 fails on any
  when the batch's gates say require_bpu_compute (new in gates.yaml; frozen batches without it are not judged)
- batch creation freezes agent/speed_ref/<job>.json into G4: latency_budget_ms = 1.5 x board_latency_ms (median
  board latency of plain int8 builds) and cpu_fp32_latency_ms; G4 also fails when the model is not faster than
  the original FP32 model on the board CPU, and records the speedup
- scripts/board_refs.py computes both; the CPU number is onnxruntime on the board itself under the board lease
- e2e prompt states the three rules; agent/VERSION 25

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:41:02 +08:00
bench
ff3c8926df Revert the pose evaluator edit from 8a1ee24: running batches froze its checksum
harness/eval/coco_extra.py is frozen per batch by task_contract (only listed equivalent rewrites may replace it).
The 8a1ee24 edit made every pose stage of the pilot batches fail the contract check (Qwen rtmpose.s never got a
formal stage). The keypoint shift gate it fed was removed in e0c224f, so the shift reaching 'unverified' no longer
decides anything; back to the approved version 505d37.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:15:37 +08:00
bench
a0e86e71ea health_check: alert on board_offline stage failures and on unreachable board ports
10-23 08:00-11:00 all 8 boards behind rdk-sandbox refused connections; board/eval steps failed as
board_offline for 3 hours and nothing in the check covered it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 11:19:15 +08:00
bench
e0c224f881 Pose: keypoint shift is recorded, no longer a pass/fail gate
The 2 px limit was a hand-set number from the first baseline (9-15): mean distance of all 17 joints in raw image
pixels, invisible joints included, not scale-normalized. On 10-22 SimpleBaseline r101 failed it with OKS-AP 68.34
vs FP32 68.22. OKS-AP already scores the task against ground truth with person-scale normalization, and FP32/quant
agreement is G2's job. New runs drop it from G3; the shift is still measured and recorded. Pose contracts no
longer state it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 07:55:51 +08:00
bench
8a1ee24338 Pose shift check no longer requires official_model; pose contracts state the 2 px keypoint shift limit
RTMPose evidence never carried official_model, so the top-down shift check reported every rtmpose run
UNVERIFIED (06 x2, pilot x2). run_quant already rejects a baseline of another model, so the key added nothing.
The contracts now say G3 also bounds the mean keypoint shift (2 px), which pilot agents could not know.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 01:39:15 +08:00
bench
8fb9349907 Agent no longer gets the platform's model code; each task states its I/O contract
The agent could read and copy harness/adapters (model loading, preprocessing, export, decoding), and every
bench dev container carried the whole harness, registry, scripts and export trees, evaluator and gates
included. That did the model-specific half of the deployment for it.

- guard and private-home jail no longer expose harness/adapters; bench dev packs only container_site
- the evaluator still decodes outputs with the platform's own code, so agent/io-contracts states what the
  graph's inputs and outputs mean (9 families, 71 models so far); the prompt appends the task's contract
- SYSTEM.md: says where official sources, weights and environments are; the compile.yaml template is
  replaced by the facts that differ from the docs
- e2e prompt: whole-class int16/float fallback and >1.5x board latency do not pass
- agent/VERSION 24

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 21:51:17 +08:00
bench
061f3ed168 opencode: hard-link the pinned node_modules into the config dir
A symlinked node_modules made OpenCode hang inside the jail (read-only
target). A hard-linked copy is an ordinary installed tree for its reify and
takes no extra disk; agent/ and runs/ share one filesystem on the VM.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 11:24:49 +08:00
bench
d166593ec6 opencode: Pi's path guard and the pinned plugin deps instead of a per-rollout install
The bench plugin applies guard-core like Pi's private-home path-guard: file
tools against the allowlist, bash only for root scans and direct shared-
resource commands; external_directory is left to that guard (job.json was
unreadable). Each rollout's config dir now links the pinned
agent/opencode/node_modules and models.json is not fetched: startup no longer
installs ~160 MB over the network.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 10:54:18 +08:00
bench
f61a083d5a opencode: export the session to a file; through a pipe it is cut at 64 KiB
Staging mobilenet.v2: 380 KB export came back as 65536 or 131072 bytes and
the rollout had no trajectory.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:40:51 +08:00
bench
a595d49c05 opencode: budget counts fresh input and output, not cached context, like Pi
A staging rollout (mobilenet.v2) hit 2M tokens at turn 63: 1.95M were cache reads
of the same context. Pi on the same task counted 120k for 96 turns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:40:51 +08:00
bench
5fb89d66b1 opencode: terminal_exec and the quota broker, like Pi
terminal_exec's body moves to agent/extensions/terminal-core.js, shared by
Pi's terminal.ts (unchanged schema/behaviour) and OpenCode's bench.ts.
OpenCode rollouts now get a managed Execution and a broker-scoped token
(the upstream key no longer enters its environment); terminal requires both.
No checkpoint/resume for OpenCode yet: the resume scan skips it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 12:46:53 +08:00
bench
44f3142cfa Reboot recovery: a reboot-killed scope proves a failed step; speed_ref sets aside an interrupted run
The 10-21 03:16 Mac mini reboot left 7 GLM rollouts (05: densenet201,
efficientnet.b2, rtmo.s; 06: rtmpose.x, rtmo.m, hypersim.base, yolo11n.seg)
quarantined OPERATION_STATE_UNKNOWN while still counted RUNNING: each had a
05-compile in flight, its reaper died with the VM before writing a receipt, and
_validate_recovered_receipt demanded one ('scope cleanup unconfirmed') although
scope_cleaned already accepts an earlier boot. Without a receipt an earlier-boot
scope now proves cleanup for a failed result and for the inline 04 whose meta is
hashed; any other success still needs its receipt.

speed_ref: stages/ref of an interrupted run kept bundle.tar, which salty_dev
creates exclusively, so the 3 in-flight references failed with FileExistsError
every 2 minutes and took all 3 workers. The leftover dir is renamed aside.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 07:38:06 +08:00
bench
e1753ad70d Salty results: fsync before rename; an empty attempt meta no longer breaks _memory
The 10-21 03:16 Mac mini reboot left zero-byte files that had been installed
(tmp write + rename, no fsync) just before: 04-calibrate/a00/meta.json of 05
cls--swin.b k2, 07-board meta/perf of 06 pose--rtmo.l k2, salty/result.json of
several dev commands. _memory json-parsed every attempt meta of the model, so
every later 04/05 of swin.b failed in 0.03 s as REMOTE_UNAVAILABLE.

_install/_fetch/dev install now fsync the data before the rename; the dev sync
manifest uses execution.atomic_json; _memory skips an unreadable meta.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 07:25:54 +08:00
bench
50f163e993 bench dev: double memory after a failed dev job; never upload the pi checkpoint temp file
A dev container OOM (no reason given, the agent cannot raise the limit) was retried
at the same size and failed again every time (10-20: efficientnet.b6 3x at 16Gi,
unidepth.v2.vit.l 2x at 32Gi). remote.json now records memory and job_state; a failed
dev job of the rollout doubles the next one's memory (cap 128Gi) and stderr says so.

.bench-session.json.tmp (pi_session atomic write) was listed then renamed away before
tar read it: FileNotFoundError, dev command died as STAGE_EXECUTOR_EXIT (3x since 10-16).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 21:02:23 +08:00
bench
19814889aa Salty worker: 06-hbm always returns its HBM/BC
The worker returned only artifacts that changed during the stage. 10-20
hrnet.w48 / ocrnet.hrnet.w18: the first 06-hbm container copied the HBM
into the (persistent) remote artifacts, then hit its memory limit; the
retry found it unchanged and never sent it, so the controller verified
'current HBM missing' and both ended UNVERIFIED after a good board eval.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 20:46:05 +08:00
bench
89c4801f53 Salty cleanup: remove the job before its storage dir
Jobs were kept until their dir delete succeeded; every storage delete
has failed server side since 10-19, so ~8000 finished jobs piled up and
from 10-20 17:00 /jobs grew past the CLI's response limit: salty ps and
describe by name failed and every Salty step ended REMOTE_UNAVAILABLE.
The job record is only an index (logs/describe are in stderr.log), so it
now goes first; the dir delete keeps its own retry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 19:47:14 +08:00
bench
f75930e0f5 Scheduler: free a board whose stage died after its cleanup was proven
A 07-board step killed at its phase deadline never reached the lease release,
and a board lease was only freed once the whole rollout ended, so two S600
boards stayed locked for 11 hours (10-20). A board slot is now reused when its
holder is dead, the stage is DONE with cleanup VERIFIED, and every board-guard
receipt says VERIFIED - the same proof the stage worker already requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 15:21:32 +08:00
bench
36432d1c4e Salty cleanup: drop a succeeded delete task's record
Retries add a task record each (storage tasks lists them all). Once a delete
succeeded its record goes via storage rm-task (data untouched; the ID stays in
the receipt). Failed records stay for the Salty side's server investigation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 14:08:53 +08:00
bench
77031cd05b Salty cleanup: refused or failed deletes are retried from the background
With Salty 0.2.4 a delete is a background task; since 10-19 every one fails
server side, and a failure was recorded once and never retried, so garbage
would pile up for good. Now a submission the server refused (an HTTP error
such as 405) or a task that failed/was interrupted is submitted again by the
reaper after 30 min, doubling to 6 h; a task failing with not_found means an
earlier try removed it. A submission with no reply stays unknown and is never
resent blindly. The result path still makes one try. The reaper also covers
ended jobs ps no longer lists, logs only removals, and salty_offload gains
--reap-only so staging gets a background cleaner without archive/export.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 14:02:07 +08:00
bench
5998ab4c81 fix(staging): support Salty CLI 0.2.4 lifecycle 2026-10-20 13:52:49 +08:00
bench
b4c4b83a88 Process reaper: a process exiting mid-scan is not a cleanup failure
On board kernels without /proc/<pid>/task/*/children, children() scans /proc and
reads each stat; a process that exits between the listing and the read answers
ESRCH (ProcessLookupError), which was not caught. 10-20 staging: the board guard
crashed in its own cleanup after a 20-minute self-test, wrote no result, and the
platform recorded BOARD_CLEANUP_UNCONFIRMED, quarantining a 5-hour rollout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 03:35:59 +08:00
bench
4b5b118909 terminal_exec: wait for a ticket queued behind the rollout's own worker
The stage worker runs one ticket at a time, but terminal_exec wait_handle gave up
after 1 s if the ticket had no operation yet ("Unknown protected stage handle").
10-20 staging: `bench stage run baseline` during a 40-minute bench dev compile,
and the agent followed the printed "# Pi wait" hint straight into that error.
In the last 3 days 85% of these errors (production 05/06 and staging) were real,
submitted tickets. A submitted ticket now waits under the execution's own stop
and deadline checks; a ticket the worker rejected before admission says why;
a handle that was never submitted is still unknown.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 01:55:47 +08:00
bench
37df6933d7 Board commands: time starts with the board; a stage's own verdict is kept
10-19 staging: a 25-minute board self-test spent all of it queued for an S600
board shared with production, and the child's TERMINAL_DEADLINE_EXCEEDED was
overwritten by a bare STAGE_EXECUTOR_EXIT because it exited nonzero. The queue
is now covered by the request deadline (as for bench dev) and the command's
time starts at acquisition; a DONE status written by the child stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 23:07:10 +08:00
bench
45dcce1e7d Salty cleanup: one try, never hold a result back
From 16:50 on 10-19 Salty's storage rm answered 405 for every object; the
cleanup retried it for 30 minutes before each stage or bench dev result went
back. Garbage removal now tries once (dir first, so a failure leaves the job
listed) and salty_offload.reap_orphans tries again on its next pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 17:29:53 +08:00
bench
f6a8318891 Tests: real Pi compacts a request the account refuses, and runs bash through the agent shell
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:56:46 +08:00
bench
ed962b11cc Agent commands: say when an earlier pipeline step failed
Pi's bash tool (shellPath), bench dev and the board terminal run commands with
pipe-note.sh: the exit code stays the last step's (no pipefail, so | head is
still 0), and a failed earlier step of the final pipeline gets one stderr line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:52:42 +08:00
bench
6e1668c9a8 Quota: a request over the account's limit is a full context for Pi
Recorded FAILED CONTEXT_TOO_LONG like a provider overflow and answered with
the overflow body, so Pi compacts and continues instead of ending the rollout
on an unrecognised 413. Content review keeps its REQUEST_EXCEEDS_INTERNAL_TPM.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:52:42 +08:00
bench
db5a7a839d Export: read the running checkout's own state wherever it lives
A checkout whose state is elsewhere (BENCH_STATE_DIR, staging) was read as
<checkout>/state, so content review and export found no database and called
a PASS rollout unfinished. One helper, paths.state_dir, used by every lookup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:52:42 +08:00
bench
20c876fd5c Staging: one rollout storage for bench dev and pipeline stages; log why paused rollouts wait
Codex review of the staging collector (10-19): a model built in bench dev was missing for 04-calibrate,
because only bench dev requests were rewritten to the container's bench/runs (reverts 56230c0). The
container now links the controller checkout's own runs/ to the same personal storage, so every
absolute path resolves alike; a no-op for production's bench/. And a paused rollout that waited ~2 h
left no trace of why: the collector logs each change of its wait reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 14:21:38 +08:00
bench
752943baaf Quota: each resume or restart starts a fresh wait allowance
Staging (10-19 14:06): a rollout whose lifetime wait total had passed wait_budget_s paused the first
time it was not admitted, resumed uncounted, and paused again every minute, starving the other paused
rollouts. 7 executions in production's s600 group are already over the total. The per-call bound and
the HTTP attempt budget are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 14:15:34 +08:00
bench
787f61fa80 Restart recovery: a dead collector's cut-off request replays at once, without pausing the shared group
Staging handover (10-19 11:40): the 2-minute hold on the dead collector's requests expired into an
unknown-outcome group pause that bounced every rollout already resumed. Its process exit closed the
connections, so the reply was cut off, not in doubt; and a platform restart no longer spends the
rollout's resume budget.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 14:03:04 +08:00
bench
c575ea0baf Restart recovery: resume turns queued for admission, wait for exiting stage reapers
Staging kill -9 with an immediate restart (10-19 11:17): a turn waiting behind the group's concurrency
read as not resumable and lost its slot, and a calibrate step whose executor was still exiting got
quarantined as SIDE_EFFECT_UNKNOWN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 11:25:40 +08:00
bench
72912a6b17 Restart recovery: keep slots for cut-off replies, wait for exiting reapers
Found on the staging collector (10-19): after kill -9 two rollouts whose reply was cut off were read as
not resumable for request_total_s while new rollouts took their slots, and a rollout handed over with a
bash command running was quarantined because the next collector looked before the reaper finished.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 11:02:59 +08:00
bench
0da66edde0 Resume rollouts after the collector dies (crash, kill, reboot, planned handover)
Processes are disposable; rollout state is resumable. When the collector dies,
the next one reconciles each running rollout from durable state instead of
quarantining or losing it:

- execution: a process of an earlier boot on this host is DEAD; a top-level
  reaper whose owner (the collector) died still proves its subtree empty
  (scopes record the owner that started them); reconcile() pauses a rollout
  with a proven-clean crash checkpoint as CONTROLLER_RESTARTED and marks its
  running tool calls INTERRUPTED; resume() across a reboot rebases monotonic
  clocks by wall time and credits the downtime as a pause
- stageworker.settle_interrupted: an admitted step whose executor is gone ends
  as STAGE_EXECUTOR_EXIT (free compile) and its handle is told directly; a
  board step without a clean board receipt still quarantines; nothing replays
- collection_runtime.crash_checkpoint: capture the real system prompt, freeze
  the session at the last saved message (mid-work phases only); configure_pi
  skips a generation ID the ledger already completed
- pi_session.js: checkpoint after every saved message (and compaction); on a
  recovered resume drop an unfinished trailing reply and answer open tool
  calls with an honest "interrupted by a platform restart" result
- scheduler: a paused rollout's local slot held by a dead holder is released
  once every process is proven gone
- pipeline: SIGUSR1 = planned handover (stop claiming, let board steps
  finish, shorten in-flight request holds, exit); SIGTERM still drains
- export: bench_recovery closes the cut segment; the dropped unfinished reply
  is excluded (UNFINISHED_BEFORE_RESTART)
- tests: test_controller_restart (real Pi on Linux: kill -9 mid-command,
  kill -9 mid-reply, SIGUSR1 handover, power loss + reboot), test_settle_
  interrupted; three tests of the old quarantine-everything rule now assert
  the new outcome while keeping their guarantees (no replay, unrelated PID
  untouched, board lease kept)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 09:29:26 +08:00
bench
6c7b19f616 offload: delete a rollout's compile scratch once it is archived
hb_compile's working_dir lives on the VM's own disk (work_root) and only
05-compile/06-hbm read it. Nothing removed it: on 10-18 742 finished rollouts
held 36 GB there, the Mac mini disk (which backs the VM disk) neared full,
and the VM's disk went read-only at 18:46.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 23:55:11 +08:00
bench
6437b572a2 fix: freeze long Pi sessions at rollout end (no 1 MiB cap)
freeze_checkpoint read the session through config_bytes, which caps files at
1 MiB for tickets/configs. Long rollouts pass that, so finalization failed:
10-15..10-17, 17 rollouts, 4 recorded INFRA_ERROR instead of their real
outcome. The session read keeps the symlink/regular-file checks, no cap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 10:33:37 +08:00
bench
18379401e4 v23: hand context compaction back to Pi, cut process rules from the prompt
- broker: a context-window 400 fails its generation (fences nothing) and goes
  back to Pi as context_length_exceeded, so Pi compacts and resends
- runner: new generation ID after compaction, wait for Pi's resumed run,
  record kept_messages; drop agent/context-mask.js and context_mask_chars
- models.json: contextWindow large so Pi compacts only on a real overflow,
  never on an estimate right before a pause (resume would not match)
- export: compactions[] gives what the model actually saw after each one
- prompt: keep facts and acceptance, drop how-to rules and coaching
  (SYSTEM.md 89->64 lines, e2e.md 27->20); stage status == stage wait

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 17:04:58 +08:00
bench
f2322ac926 test_pi_session:真 Pi 0.73.1 下 context_mask_chars 让请求里出现占位、最近输出完整、会话文件不变
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:49:58 +08:00
bench
b248a28fd7 上下文满记为预算用完;broker 内部错误可续跑并记日志;断线只占账号 2 分钟;04 Qwen 只发出时省去最早的工具输出
- quota:400 且正文说上下文超长(vLLM maximum context length、GLM exceeds max length)记 CONTEXT_TOO_LONG,不续跑;
  rollout 结束记 CONTEXT_BUDGET_EXHAUSTED(结局 BUDGET_EXHAUSTED,rollout.json TIMEOUT),不再是 INFRA。10-16 当天 7 条 Qwen。
- quota:do_POST 吞掉的异常打出类型、消息、位置(不含请求);一次都没发出去的 generation 记 BROKER_ERROR 暂停,
  能像连不上一样续跑。10-16 05 hrnet.w32 白跑 2.9h。
- quota:连接被断(REQUEST_CONNECTION_INTERRUPTED)的请求只占账号 UNKNOWN_HOLD_S=120 秒,不再等到请求自己的期限
  (20–27 分钟、整个账号的轨迹全停)。
- agent/context-mask.js:配置 rollouts.context_mask_chars 时(只给 04 Qwen),发出的上下文超过这个字数就把最早的工具输出
  换成占位,降到 60% 以下;会话文件保留原文;切点只在再次超限时移动。Pi 自带压缩只在两次 prompt 之间触发,用不上。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:37:55 +08:00
bench
21fce5e2e0 v22:bench stage wait 只看一眼不轮询;板上自测先查大小、拒绝有原因、失败也删副本;速度参考编不出来写 unavailable
- bench stage wait(stageclient 与 stagerun 两个入口)不再睡,没结束就返回 2 并指向 terminal_exec wait_handle。
  10-16 efficientvit.b0 400 轮里 307 轮是轮询。
- bench dev --board:先用 salty storage ls 量开发环境里的目录(>512 MiB 或 >40 个子目录直接拒绝),
  取回后已到时限也明确拒绝;拒绝原因作为命令结果回给 agent;snapshot/dev-files/tar 在任何路径都删。
  10-16 四次自测三次从 1.2 GB 的目录提交,取回 40 分钟、超时、exit 2 无原因、VM 留下 2.5 GB。
- speed_ref:默认配置编不出来时写 latency_ms_est=null、status=unavailable,并补齐以前的 FAILED。
- SYSTEM.md 对应三处;agent/VERSION 22。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:24:22 +08:00
bench
e543d7bd5f bench stage wait 一次最多等 10 分钟(原 60 秒),结束就返回
10-16:轮询的 agent 每分钟烧一轮,efficientvit.b0(v18)400 轮里 302 轮是 bench stage wait,没编译就用完预算;
vkitti.base 73 轮、zoedepth.nk 55 轮。bash 一条命令上限约 14 分钟,10 分钟在内。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 06:39:50 +08:00