Repository navigation
test(tunnel): witness shared backpressure at a fixed feedback checkpoint - #57
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
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.
Scope
Test-oracle correction, witness helpers and architecture documentation; production pacing code and defaults are unchanged.
The first post-merge main CI failure 37096880419 is preserved and was not rerun. In a separate predeclared, instrumented 12 ms warmup condition, 4 of 10 terminal-target assertions failed despite actual acceptance of eight lower-capacity samples, followed by permitted higher pacing-limited delivery samples. This demonstrates an endpoint-oracle gap, not the exact cause of the original CI failure or a production pacing defect.
Changes
Validation
Local commands overlapped and are correctness checks, not performance measurements. No remote SSH, browser/corpus comparison, release, tag or registry publication. Fresh PR and subsequent main checks are still required.