Command Info

Name: linksite:jp-bench-watch

Description: Periodically evaluate JP bench orchestration progress until landing is complete

Status: failed

Start Time: 2026-08-17 11:29:08

End Time: 2026-08-17 11:29:08

Total Time: 0 seconds

Dispatched Jobs Count: 0

Successful Jobs Count: 0

Failed Jobs Count: 0

Output

11:29:08 Lock acquired for command: linksite:jp-bench-watch
11:29:08 [2026-08-17T11:29:08+00:00] JP bench 29/51 scored (56.9%) · missing 22
orchestrator: not detected
next cell: jp-2 × moonshotai/kimi-k2.6
gaps (43):
· [info] jp-1: A/B comparison ready (6 challengers + baseline)
· [medium] jp-2: missing 2 challenger(s): moonshotai/kimi-k2.6, fugu-ultra
· [info] jp-2: A/B comparison ready (3 challengers + baseline)
· [medium] jp-3: missing 2 challenger(s): moonshotai/kimi-k2.6, fugu-ultra
· [info] jp-3: A/B comparison ready (3 challengers + baseline)
· [medium] jp-4: missing 2 challenger(s): moonshotai/kimi-k2.6, fugu-ultra
· … +37 more (see gaps report file)
improvements (6):
· [medium] aisubscription: avg 28.303070094188min/cell — consider timeout headroom or faster judge (bench already uses fixed GLM judge)
· [medium] moonshotai/kimi-k2.6: avg 91.828335563342min/cell — consider timeout headroom or faster judge (bench already uses fixed GLM judge)
· [medium] deepseek/deepseek-v3.2: avg 30.588510532512min/cell — consider timeout headroom or faster judge (bench already uses fixed GLM judge)
· [medium] fugu-ultra: avg 68.812861482302min/cell — consider timeout headroom or faster judge (bench already uses fixed GLM judge)
· [info] clobbering_inflight ×5 in recent logs — Eval dispatch clobbered an in-flight run — run docs should isolate, verify aggregator
11:29:08 Lock released for linksite:jp-bench-watch
11:29:08 Command linksite:jp-bench-watch failed with exit code 1.