Repository navigation
bench: re-anchor the returning host until its trim is stable - #308
Merged
Merged
Conversation
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
1 participant
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.
The tracker test sent exactly two CAL trains when the host returned to true baud. Protocol sec 9.3 defines converged as trim_steps stable between trains, so the return now reuses anchor() until two read-backs agree, with the same ANCHOR_TRAINS_MAX bound. The assertion reports the train count.
Bench gate (pre-registered): detune x10 at 1M and x10 at 3M on main 2ee1321 with this test: >= 9/10 each with no "re-anchors" red; train counts reported.
https://claude.ai/code/session_016NV5eybqhfjQPnesWHUCRs