Repository navigation
fix: import the effective Telegram timing observation - #77
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.
Telegram QA evidence now contains both status-only observations and an aggregate timing observation for the same scenario. The importer selected the first observation and failed with
telegram-reply-chain-exact-marker is missing result.timing, despite valid 20-sample measurements later in the artifact.Select the unique effective timing observation, reject ambiguous measurements, and preserve failures from other effective observations. Superseded observations do not override current evidence. Both Main RTT and Release RTT use this importer.
Validation: all 11 importer tests pass, including status-only observations before and after timing, failed observations, superseded timing, and ambiguous timing. Independent code review completed without actionable findings.
Failure evidence: https://github.com/openclaw/openclaw-rtt/actions/runs/36798382953 and https://github.com/openclaw/openclaw-rtt/actions/runs/36759155604.