Repository navigation
test(omo): wait for the observed pane label - #1097
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 16 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Fix the intermittent
server/omo.contract.test.ts:52failure in “labels a running omo pane when herdr supplies no agent kind”.Root cause and evidence
The fixture waits for its script path in one herdr
pane.process_inforesponse, butlabelOmoPanesperforms a separate fresh process probe. The fixture marker is not a readiness barrier for that probe: a missing matching foreground process or a failed probe leaves the original snapshot's agent undefined. The test asserted the first label sample immediately instead of waiting for the state it describes.Main run 38555205694 on October 14, 2026 failed after 199.60 ms: expected
"omo", receivedundefinedat line 52:77. Five local pre-fix isolated runs passed, including an attempted concurrent unit-suite load, so the failure remained intermittent locally. The CI log and the two independent process probes establish the synchronization gap without guessing which negative-probe branch occurred.Open PRs #984 and #985 do not touch this test. PR #923 changes custom OmO runtime recognition but leaves this one-shot assertion unchanged, so this is not a duplicate.
Fix
Poll the exact labeled state with a bounded five-second deadline and 50 ms interval. The same original snapshot is retained, so all three existing assertions still prove that herdr supplied no agent kind, the derived snapshot is labeled
omo, and the input snapshot is not mutated. No assertion retry, timeout increase, fixed sleep, production change, or changelog entry.Verification
CHECK_WAIT_SECONDS=3600 bun run check run bash -c 'for i in 1 2 3 4 5; do bun test --timeout 15000 ./server/omo.contract.test.ts || exit 1; done'. Report:23297fbe-e853-45cf-ad71-a4c6990b77e0.bun run check fastpassed on the same source fingerprint. Generated types, typecheck, build, and unit tests all passed: 3,574 passed, 50 skipped, 0 failed. Report:19778f35-f21d-4c74-987e-9c48ae6620a9.git diff --checkpassed. Toolchain: Bun 1.4.2, Node 22.23.1, herdr 0.9.3, macOS arm64.The lane handoff records the root cause, CI timing evidence, diff, full verification log references, and this PR URL at
.omo/mass-ulw/2026-10-14/A3.md.