igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

miner-faults register: run 5 (card-appears green with the fixed listing); every class's injector step passes on engine 073fbea1

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
(cherry picked from commit ee3d93386b7aabe8188fd2c8bd00c63a818ac2bf)
This commit is contained in:
igneum-labs 2026-10-07 12:53:56 +00:00
parent 44d2def1e5
commit 26574c32d0
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/plans/miner-faults.md
View file

@ -47,8 +47,8 @@ f067f7c1).
Injector, run 4 on a one-shot RunPod pod (RTX 3070, Ubuntu 24.04, 7 October 2026 12:19Z to 12:48Z, engine 89d117ce,
the 0.3.17-line miner, the stand-in worker; the pod's real GPU switched off through the app's own card path; the private
node on devnet suffix 9960 with a 2-thread CPU block producer): seven of eight steps PASS, one on the stand-in's listing
(fixed at ecd79874, rerun below).
node on devnet suffix 9960 with a 2-thread CPU block producer): seven of eight steps PASS, the eighth on its rerun (run 5,
the stand-in's listing fixed at ecd79874): every class's step is green.
| Step | Class | Result | Seconds |
|---|---|---|---|
@ -59,7 +59,7 @@ node on devnet suffix 9960 with a 2-thread CPU block producer): seven of eight s
| node-silent | node watchdog | the node stopped with SIGSTOP: restarted by the app (120 s rule plus the 30 s terminate grace), synced, mining again | quiet to restart 150.3; restart to synced 7.0; quiet to mining 170.4 |
| one-card-fails | MF-4 | two new cards listed, two healthy ones mining, the third held 30 minutes with "not usable on this driver: <the self-test line>", the healthy two still mining 90 s on, the pack exported once and reused 7 times | listed 48.1; two mining 48.1 |
| orphan-miner | MF-7 | a stray igneum-miner on the engine's node killed by the minute sweep, one log line per kill, the engine's own miner left alone | inject to kill 21.1 |
| card-appears | MF-3 | run 4: the card that appeared was listed (40.1 s) and mined with no tap (50.1 s); the card that left was NOT marked removed: the stand-in's `--list` lacked the real worker's header line, which the engine reads as "the tool did not answer" (right for a crashed driver). Rerun with the header (ecd79874): see run 5 | |
| card-appears | MF-3 | run 5 (12:48Z to 12:53Z, the stand-in's listing with the real worker's header, ecd79874): a second card appeared and was listed, its worker started with no tap; it left and was marked removed while the other card kept mining; it came back and mined again with no tap. Run 4 had failed the removal because the stand-in's `--list` lacked the header line, which the engine reads as "the tool did not answer" and removes nothing on (the right call for a crashed driver) | listed 40.1 after it appeared; mining 50.1; marked removed 50.1 after it left; mining again 72.2 after it came back |
FAULT lines the engine posted to the intake in run 4: 13 (watchdog, worker-fault, node-exit, orphan-miner classes).