You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mythic Masters walk together: the Chrome journey's "a friend walks up, the contract comes back" step timed out once in two builder runs #3858
apps/mythic-masters/test/together.test.ts, the last step: A jumps to a board (the room stops vouching), takes its contract, B jogs over in 5 m hops every 220 ms, and B should see A's contract at stage 0 once the room vouches for A again.
On the builder (Bob) during round 16 of #3792, one run of two failed there with error: still null at line 112 after the 12 s wait; the rerun passed (86.8 s). Main passed the same test once before that. The change in that round (a pick or flush is told only from beside it) doesn't touch the vouch path, so this looks like timing: under load, B's pose may land beside A only late in the hops, or A's retell may queue behind the room's rate limit (a seen catch-up costs up to 8 tokens of a burst of 16).
To do: log what the room sends A (vouch or not) when the step fails, then either fix the cause or wait for vouch before the 12 s clock starts.
Issue-runner check (2026-11-06): the cause is found and fixed in #3861 (merged at 09:37, two minutes after this was filed, so the failing run didn't have it). With temporary logs in region.ts, the room never got B within 80 m of A: on its hops, B met a wild creature, lost, and the Book's "downed-first" talk held its poses back. So the room never vouched for A, and the contract stayed null. Whether a wild one meets B is random, which fits one failure in two runs. #3861 has both pages walk in peace for that scene.
Since then: two runs in a row on the builder pass (65.1 s and 65.2 s). Nothing left; it's open only for the owner to close.
Done, from the 2026-11-09 board scan (notes/audit/2026-11-09-*.json): Cause found and fixed in #3861 (merged): the trust scene walks in peace; two builder runs in a row pass
Activity
QuinnsCode commentedon Nov 6, 2026
Issue-runner check (2026-11-06): the cause is found and fixed in #3861 (merged at 09:37, two minutes after this was filed, so the failing run didn't have it). With temporary logs in
region.ts, the room never got B within 80 m of A: on its hops, B met a wild creature, lost, and the Book's "downed-first" talk held its poses back. So the room never vouched for A, and the contract stayednull. Whether a wild one meets B is random, which fits one failure in two runs. #3861 has both pages walk in peace for that scene.Since then: two runs in a row on the builder pass (65.1 s and 65.2 s). Nothing left; it's open only for the owner to close.
Mythic Masters walk together, round 18: the two-page journey runs on …
Mythic Masters walk together, round 18: the two-page journey runs on …
Mythic Masters walk together, round 18: the two-page journey runs on …
QuinnsCode commentedon Nov 9, 2026
Done, from the 2026-11-09 board scan (notes/audit/2026-11-09-*.json): Cause found and fixed in #3861 (merged): the trust scene walks in peace; two builder runs in a row pass