Skip to content

test(guard-patrol-template): bot-sorts-first order is a note, not a check - #592

Open
AlexZ005 wants to merge 1 commit into
mainfrom
fix/61-guard-premise
Open

AlexZ005 wants to merge 1 commit into
mainfrom
fix/61-guard-premise

Conversation

@AlexZ005

Copy link
Copy Markdown
Collaborator

On the v1.72.0 tag battery, guard-patrol-template was red on both attempts, and only on the premise "the bot's peer id sorts before the host's". The host drew low ids (04bbf, 259d2), so six bot restarts never sorted first. 5.4 (exactly ONE peer runs the guard, positions agree) passed both times.

Which id sorts first is luck, not a fault. 5.4 holds on either order, and the modules unit tests (test:navigation, the 61-int election block) cover both orders of the election. So when no bot sorts first, the order is logged as a NOTE; when one does, it is still checked.

  • One run from a snapshot of this branch: 23/0 (that run drew the bot-first order: 2e3e6 vs host 84c97).
  • Test-only. Per the small-fixes rule it rides the next release (1.73.0, 80a-int), whose battery covers it.

🤖 Generated with Claude Code

… a check

On the 1.72.0 tag battery the host drew low ids (04bbf, 259d2), so six bot restarts never sorted first and
the premise failed both attempts while 5.4 (one peer runs the guard) passed. The order is luck; 5.4 holds on
either order and the modules unit tests cover both orders of the election.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant