Playbooks 07 and 08: after a failed try, a local run of the integration level is a good first step (guideline) #471

Merged

jschoubben merged 3 commits from pb/try-fails-run-locally into main 2026-10-23 21:50:24 +00:00

Conversation 1 Commits 3 Files Changed 2

+14 -6

mesh-tools commented 2026-10-23 21:20:37 +00:00

Member

Copy Link

Copy Source

The operator, 2026-10-23 23:18: "if it fails, you should run it locally" — and then: "don't turn such stuff into a 'rule' per se, it's more of a guideline".

A verdict names only the first failed test (issue 1921), so after R4g's hand merge its faults surfaced one per try until a local run of mesh-delivery's integration level listed them all in a minute; the controller's local run did the same (issue 1931) and measured its level at about a minute (issue 1930).

Playbook 08 step 5 and playbook 07's fixing-agent brief now say, as a guideline: after a failed try or check it usually pays to run that repository's whole integration level locally before another try. Playbook 07's two 'never run integration tests on the machine' lines now say 'while developing', so the default (the try runs them) and the guideline agree.

hq's checks (go test ./... at the root) pass locally.

Reviewed-by: review-471@shanks at 8055006ba1
Pushed-by: lead-47@shanks

The operator, 2026-10-23 23:18: "if it fails, you should run it locally" — and then: "don't turn such stuff into a 'rule' per se, it's more of a guideline". A verdict names only the first failed test (issue 1921), so after R4g's hand merge its faults surfaced one per try until a local run of mesh-delivery's integration level listed them all in a minute; the controller's local run did the same (issue 1931) and measured its level at about a minute (issue 1930). Playbook 08 step 5 and playbook 07's fixing-agent brief now say, as a guideline: after a failed try or check it usually pays to run that repository's whole integration level locally before another try. Playbook 07's two 'never run integration tests on the machine' lines now say 'while developing', so the default (the try runs them) and the guideline agree. hq's checks (`go test ./...` at the root) pass locally. Reviewed-by: review-471@shanks at 8055006ba1f31ad92338d2ce9808e7686efb4928 Pushed-by: lead-47@shanks

mesh-tools added 1 commit 2026-10-23 21:20:37 +00:00

Playbooks 07 and 08: a failed try or check is run locally at once, so every failure shows in one run, not one per try (the operator, 2026-10-23) 87c338da8e

mesh-tools commented 2026-10-23 21:20:43 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/hq@8055006ba1f3 — delivered since 2026-10-23T21:50:25Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

• 2026-10-23 21:24 (new) → proposed (announced): novox/hq#471's head announced
• 2026-10-23 21:24 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-23 21:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-23 21:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-23 21:50 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@8055006ba1f3` — **delivered** since 2026-10-23T21:50:25Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-23 21:24 (new) → proposed (announced): novox/hq#471's head announced - 2026-10-23 21:24 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-23 21:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-23 21:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-23 21:50 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-23 21:22:23 +00:00

Playbooks 07 and 08: say the local run after a failed try as a guideline, not a rule (the operator) 2b53b6a5d2

mesh-tools changed title from Playbooks 07 and 08: a failed try or check is run locally at once to Playbooks 07 and 08: after a failed try, a local run of the integration level is a good first step (guideline) 2026-10-23 21:22:30 +00:00

jschoubben added 1 commit 2026-10-23 21:24:18 +00:00

Playbook 07: the two 'never run integration tests on the machine' lines say 'while developing', so the guideline after a failed try no longer contradicts them (review-471) 8055006ba1

jschoubben merged commit 82aa3f6afa into main 2026-10-23 21:50:24 +00:00

jschoubben deleted branch pb/try-fails-run-locally 2026-10-23 21:50:24 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#471