test(compat): lossmaxttl baseline A/B calibration + gain-hunt scaffold - #38
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.
Affected repo & language: srtla — C / compat test harness
What
Adds two compat-test additions backing the receiver-capability reconciliation:
lossmaxttl30-vs-40 baseline calibration A/B scenario (Task 1).(Task 2).
Why
The reconciliation needs an empirical baseline winner. The A/B calibration
proves 30 and 40 tie at zero drop/errors, so the pre-registered tie-break
resolves to
lossmaxttl=40(BellaBox parity). The gain-hunt scaffold makesfuture FEC/parameter gain experiments reproducible. See
docs/RECEIVER-RECONCILIATION.mdanddocs/GAIN-HUNT-PROTOCOL.md.How to verify
cmake -B build && cmake --build buildthenctest.total=9 passed=6 failed=0 skipped=3—see
test-results/recon-2.log/recon-11.log.Risks
None — test-harness and docs only. No receiver/sender runtime change.