vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

memory: h2o judge investigation closed — v1 note question was the cause, re-fitted in albok-nemi 0.1.18; eval seat down

Browse Source
This commit is contained in:
vh
2026-10-12 16:20:49 -07:00
parent 2b40805b84
commit 8d9fcd9ffb
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/h2o-eval/README.md
+4 -1
View File
@@ -1,6 +1,9 @@
# h2o-eval (TEMPORARY) — fv-ml1 GPU 3, :8034
> **UP again since 2026-10-12 1428 PT, round 2** (Prime 1420, via albok-dev): "I'd like to understand why h2o failed, so
> **DOWN since 2026-10-12 1619 PT** (round 2 done: the floor was ruled out, with identical verdicts on and off, and albok-nemi 0.1.18
> re-fitted the judge's note question). The host keeps `/opt/docker/compose/h2o-eval` and the weights.
>
> **Round 2 (was UP 2026-10-12 1428–1619 PT)** (Prime 1420, via albok-dev): "I'd like to understand why h2o failed, so
> stand it up on gpu3 and refit it and let's get an understanding." albok-dev runs the investigation and the judge
> re-fit (thread `01M4S026GWS354WZGXZ5E34F31`). **No load tests or other traffic while their runs are in.** Round 1
> (1300–1319) was the pre-cutover validation. Take it down with `docker compose down` when albok-dev is done.