RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(runicnpc): 9c, the first drill that failed (runicnpc-rust#20) #408

Merged
whitlocktech merged 2 commits from docs/runicnpc-staging-drill-20 into main 2026-11-01 02:18:04 -06:00
Conversation 0 Commits 2 Files Changed 1 +8 -5
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit c576cac033 - Show all commits

13
runicnpc/PLAN.md
View File

@@ -1758,11 +1758,14 @@ found below; two checks are not explained yet (the last item).
(`<group>.exception`), and the run goes on to `# done all`.
- **The drill's rig kept data a fresh server would not have.** `s6.examples.fullCondition` failed on kits that an
older build had written: RunicNPC writes its example kits once, into Kits' own file (D284), and the drill
removed only the harness's files before a run. It now also deletes Kits' `kits_data.json` and RunicNPC's
`profiles`, `placements`, `routes` and `state` files, so `rust-staging` boots like a new server and the first
load writes the examples again at this Rust's durabilities (D324) and settles the Kits reload (D329). Files
only, never a directory the panel would create (§1.5); the `rnhrevolver` kit is added after RunicNPC's first
load, as before.
removed only the harness's files before a run. It now also deletes RunicNPC's `profiles`, `placements`,
`routes` and `state` files and replaces Kits' `kits_data.json` with one holding only the harness's hidden
`rnhrevolver` kit, so `rust-staging` boots like a new server: Kits reads that kit at boot, and RunicNPC's first
load adds the examples beside it at this Rust's durabilities (D324) and settles the Kits reload (D329). Files
only, never a directory the panel would create (§1.5). The first try deleted Kits' file and added the kit
after boot with `oxide.reload Kits` through the panel's command endpoint; that reload never happened (run 48,
#22: no compile job, every test profile refused for want of the kit). The add-after-boot stays as a fallback,
now through the console's websocket, and is a finding when Kits does not load again.
- **The drill stops waiting when the harness has.** If the harness's file gets no new line for 5 minutes, the
finding reads "The harness stopped after `<last line>` (no output for 5 minutes; N pass, M fail so far)." The 45
minutes stays as the cap for a harness that is still writing. Whenever the harness did not finish, the tail of