jschoubben
407416e6d0
Seen twice today. Once mid-run: thirteen passes, then the process ended with no summary, no failure and no receipt. Once from the start: the first test ran 35 minutes against a measured 4.5 and was still running when it was stopped. Ruled out rather than assumed: not memory (84 GiB free, no OOM), not the daemon (the stalled machine answered `incus exec` immediately), and not the changes under test — the anchor VM had no host log and no containers, so the run never reached placing the host. What changed just before is that the rebuild went from two artifacts to six, and every one of them is pushed into the scenario's registry, which is the step the second stall sat in. Recorded as what changed, not as the diagnosis. The reason this is an issue and not a slow test: the suite prints nothing between starting a scenario and finishing its first test, so four minutes and thirty-five look identical from outside, and the only recourse is to guess. That is how a workstation was left unbootable in August. And a run that ends silently after thirteen passes is a run somebody may believe.
04-ISSUES
The front door for "something is wrong" at the level of the mesh's design or governance. Diagnosis happens here, where the whole mesh is in view; the fix lands in the owning code repository.
What belongs here
| Belongs here | Belongs in the knowledge base |
|---|---|
| The design permits a failure to be silent | How to fix one occurrence of it |
| A documented rule is enforced by nothing | A command that works around it |
| A stated invariant is false in practice | A node-specific quirk |
| The owner is unknown and finding it needs the whole mesh in view | Symptom → fix, once the answer is known |
The knowledge base already holds the operational record and is indexed on symptoms. This folder is not a second copy of it. An issue here is a question HQ must answer; an entry there is an incident someone must clear. An issue whose answer is a general lesson belongs in both.
Structure
NNN-short-name/
00-report.md the symptom as observed, with the evidence; status in frontmatter
01-diagnosis.md the investigation trail, dated, including what was ruled out
Frontmatter, on 00-report.md
---
status: open | diagnosing | located | resolved | wontfix
opened: YYYY-MM-DD
located-in: [] # owning repo(s) or module(s), filled by diagnosis
fixed-by: # pull request or commit reference, filled at resolution
amended-design: # design doc path, when the root cause was a design gap
---
Rules
- Anyone may open an issue. No localisation is required to report one.
- The full flow is playbook
00-META/process/03-issues.md. - Closed issues are never deleted — they are the mesh's symptom-to-component memory.
wontfixis legitimate and requires a sentence saying why.